Skip to main content
In a few minutes you will check your API key, read your organization and read its usage this month. Each step shows the call in curl, Python, PHP and JavaScript; choose your language once and every step follows it.
You need an API key of your organization. If you have none, create one and put it in the environment variable RFC_API_KEY:
1

Check your key

Get the calling credential answers who your key is. It counts against no limit.
The answer starts like this:
It goes on with limits, your key’s calls a minute, and remaining, the calls it may still make now (see Rate limits). Keep org.id: it is the orgId of every other path.
2

Read your organization

Get the organization reads its name, its slug and its currency.
3

Read this month's usage

Get this month’s usage answers, for each module, how many of each unit the organization used this month (count), its free allowance (freeAllowance) and what is left of it (left).
Your key works. A call that fails answers application/problem+json with a code that says why: see Errors.

Next steps

Errors

The shape of every error, and what to do with the common ones.

Pagination

Read a whole list, a page at a time.

Rate limits

The calls a key may make, and how to retry a write safely.

API reference

Every operation, with its fields, its errors and examples.