SimpleLLMDocs
HTTP API
Markdown ↗

Read current key metadata

GET /v1/keys/current

Base URL: https://api.simplellm.eu. Authenticate using Authorization: Bearer $SIMPLELLM_API_KEY.

Example request

bash
curl --fail-with-body https://api.simplellm.eu/v1/keys/current \
  -H "Authorization: Bearer $SIMPLELLM_API_KEY"

Responses

HTTP 200

Successful response

Content-Type: application/json

FieldTypeRequiredMeaning
idstringNo
user_idstringNo
key_prefixstringNoPublic prefix only, never the key secret.
namestring / nullNo
rate_limit_rpminteger / nullNo
rate_limit_tpminteger / nullNo
max_concurrentinteger / nullNo
balance_enabledbooleanNo
balance_scnumberNo
balance_limit_scnumberNo
created_atstringNo
last_used_atstring / nullNo
revoked_atstring / nullNo

Illustrative response shape only; IDs, timestamps and counters below are synthetic, not live limits or customer data.

json
{
  "id": "00000000-0000-4000-8000-000000000000",
  "user_id": "00000000-0000-4000-8000-000000000000",
  "key_prefix": "sk-example",
  "name": null,
  "rate_limit_rpm": null,
  "rate_limit_tpm": null,
  "max_concurrent": null,
  "balance_enabled": false,
  "balance_sc": 0,
  "balance_limit_sc": 0,
  "created_at": "2026-09-14T00:00:00Z",
  "last_used_at": null,
  "revoked_at": null
}

Error handling

Errors can occur in authentication, billing, routing or the upstream service; not every status applies to every route.

StatusMeaning
400Invalid request
401Invalid credentials
402Insufficient credits
403Access denied
404Model or resource not found
429Rate or capacity limit
500Internal error
502Routing or upstream error
503Temporarily unavailable
504Deployment timeout

See Troubleshooting for response examples and Rate limits & retries for retry rules.

Machine-readable schema

Download OpenAPI JSON. Operation ID: getCurrentKey.

Search the complete documentation.