Account

Allowance, rate limits and where completions are delivered.

What you have left this month, the limits that apply to your keys, and the default callback settings.

webhook_secret comes back in full. It is not a password: you already proved you hold a key for this organization, and it is what you need to verify our signature. A secret you cannot read is a secret you cannot implement against.

It is the only secret we sign with, whichever destination a completion goes to - the standing webhook_url, or a callback_url named on a single submission. Verify against this one value and you are done. It can be present while webhook_url is empty: naming a callback_url once is enough to give you deliveries to verify, and this is what signed them. Empty means no destination exists yet and there is nothing to verify.

Request #

No parameters.

Call it #

curl -X GET "https://api.easydata.win/v1/account" \
  -H "X-API-Key: $API_KEY"

Response #

{
  "data": {
    "org_id": "6b1f0e2a-3c4d-4e5f-8a9b-0c1d2e3f4a5b",
    "quota": { "unlimited": false, "limit": 25000, "used": 4182.5, "remaining": 20817.5 },
    "webhook_url": "https://app.example.com/hooks/enrichment",
    "webhook_secret": "whsec_9f2k3jd82ka0...",
    "rate_limit": {
      "requests_per_minute": 300,
      "concurrent_batches": 5,
      "sync_requests_per_minute": 60,
      "sync_concurrent_requests": 2,
      "credits_per_hour": null
    }
  },
  "meta": { "requestId": "req_8f2ka91x" }
}

Errors #

Every failure uses the same envelope, and none of them is metered - see Errors.