A REST JSON API for stats, reviews, ratings & phone

The data behind Astrina — site analytics, reviews, rating summaries, and phone intelligence — is now available to pull straight into your own code. The Developer API is a REST JSON API that hands it all back from a single key.

One key, four endpoints

The API is versioned under /api/v1 and every endpoint speaks plain JSON. Point your client at the resource you need:

• GET /api/v1/stats — analytics for a site you own: visitors, page views, top pages, sources, and countries.
• GET /api/v1/reviews — reviews plus the rating for a subject.
• GET /api/v1/rating — a rating summary with the star distribution.
• GET /api/v1/phone — phone intelligence.

On top of these, the Auth API powers "Login with Astrina", so you can add social sign-in to your own app without building an identity stack yourself.

Authenticate however fits your stack

Grab a key from /my/api.php, then send it whichever way is cleanest for your client. The API accepts three forms:

• An X-Api-Key header.
• An Authorization: Bearer token.
• An ?api_key= query parameter.

Header-based auth is the safest default for server-side code; the query parameter is handy for quick tests and browser-side calls. Responses are CORS-open, so you can call the API directly from the front end when that suits you, and they are marked noindex so your data does not leak into search engines.

Quotas and plans

Usage is metered per day, and every response tells you where you stand — each payload includes your quota usage, so you never have to guess how many calls you have left.

• Free tier: 100 calls per day.
• API plan: 10,000 calls per day for €19 per 30 days.
• Business analytics tier: API access is included.

Start on Free to prototype, then move up when your integration needs the headroom.

Predictable JSON, predictable errors

Success and failure both come back as JSON. When something goes wrong, the response carries an error field and the right HTTP status, so your error handling can branch on the status code instead of parsing strings:

• 401 — bad key.
• 429 — quota exceeded.
• 400 / 422 — bad params.

Because the quota state ships in every response, a well-behaved client can back off before it ever sees a 429.

How to get started

1. Open /my/api.php and create an API key.
2. Pick an endpoint — start with /api/v1/stats for a site you own.
3. Send your key in the X-Api-Key header and read the JSON back.

A first call is a one-liner:

curl -H "X-Api-Key: YOUR_KEY" https://astrina.io/api/v1/stats

Prefer a bearer token? Swap the header:

curl -H "Authorization: Bearer YOUR_KEY" https://astrina.io/api/v1/reviews

Or drop the key straight into the URL for a quick check:

curl "https://astrina.io/api/v1/rating?api_key=YOUR_KEY"

From there, the same pattern covers ratings and phone intelligence — one key, one header, four sources of data. Get your key and make your first call today.