Platform

System API

2 endpoints under https://api.mailneo.co/api/v2. Every request carries your key in the X-API-Key header. Start with the guide →

System
getMe

Describe the calling API key

Returns the identity, team and effective scopes of the key making the request. Scope-free: every integration can call it.

https://api.mailneo.co/api/v2
GET/meNo scope required

Example request

curl "https://api.mailneo.co/api/v2/me" \
  -H "X-API-Key: $MAILNEO_API_KEY"
Authorization
Required scope
None. Every key may call this endpoint.
Credential
X-API-Key: mk_live_...Authorization: Bearer mk_live_...
Response · 200

Success

data

FieldTypeAlways presentNotes
object"api_key" | "oauth_token"Yes
idstringYes
key_idstringYes
environment"LIVE" | "TEST"Yes
teamobjectYes
team.idstringYes
rolestringYes
role_at_issuestringYes
clientobjectNo
client.idstringYes
client.namestringYes
client.grant_idstringYes
client.resourcestringYes
api_versionstringYes
scopesstring[]Yes
granted_scopesstring[]Yes

meta

FieldTypeAlways presentNotes
request_idstringYes
System
getUsage

Read current-period usage and limits

Lets an automation self-throttle against its own quota instead of discovering the ceiling by hitting a 402.

https://api.mailneo.co/api/v2
GET/usageNo scope required

Example request

curl "https://api.mailneo.co/api/v2/usage" \
  -H "X-API-Key: $MAILNEO_API_KEY"
Authorization
Required scope
None. Every key may call this endpoint.
Credential
X-API-Key: mk_live_...Authorization: Bearer mk_live_...
Response · 200

Success

data

FieldTypeAlways presentNotes
object"usage"Yes
periodobjectYes
period.startstringYes
period.endstringYes
planstringYes
contactsobjectYes
contacts.usednumberYes
contacts.limitnumberYes
emailsobjectYes
emails.usednumberYes
emails.limitnumberYes
apiobjectYes
api.requests_per_minutenumberYes
api.max_keysnumberYes
api.send_allowedbooleanYes

meta

FieldTypeAlways presentNotes
request_idstringYes

Next Steps