Skip to main content
NaijaTaste’s public API endpoints do not require authentication. You can call any endpoint directly from any HTTP client, server-side application, or browser environment without registering for credentials or managing tokens.
No API key or token is required. You can call all endpoints directly from any HTTP client or application.

​
Making unauthenticated requests

Because no authorization header is needed, a minimal request looks like this: 
curl -X GET https://naijataste-api-vcp4.onrender.com/health
For endpoints that accept a request body, send JSON with the Content-Type header: 
curl -X POST https://naijataste-api-vcp4.onrender.com/simulate-review \
  -H "Content-Type: application/json" \
  -d '{
    "persona": {
      "avg_rating": 3.5,
      "rating_tendency": "balanced",
      "price_sensitivity": "medium",
      "tone_keywords": ["jollof", "service"],
      "total_reviews": 10,
      "sample_reviews": ["Good food and great service"]
    },
    "item_name": "Bukka Hut",
    "item_type": "restaurant",
    "location": "Victoria Island",
    "features": ["friendly staff", "local food"]
  }'
No Authorization header, bearer token, or API key is needed on any request.

​
What this means for your integration

Since the API is open, you do not need to:
  • Register for an account or API key
  • Store or rotate credentials
  • Refresh tokens or manage expiry
  • Add an Authorization header to any request
You can start making requests immediately from any environment that can send HTTP requests.
For production integrations, make sure to handle 503 errors gracefully since the API depends on external services (Google Places and Gemini AI).

​
Web app vs. direct API access

The NaijaTaste web app at https://naijataste.onrender.com handles its own session management for features like saved reviews and user profiles. This section covers direct API access only — session state from the web app does not apply when you call the API directly.