Contact

A question about the API, a response you were not expecting, an integration that stopped: write to dev@fatureihoje.com.

Write in Portuguese, English or Spanish.

Before you write

Four checks solve most cases, and what you gather along the way is exactly what support asks for afterwards.

1. Read the code in the error body. It says what happened, and it is stable. The full list, with what to do for each one, is in Errors.
2. Open View usage in the key menu. There you find the calls of the last 30 days, refused ones included, with status, source address and request_id.
3. Check the key state in the panel: Active, Rotating, Expired or Revoked.
4. Check the address. Only api.fatureihoje.com answers /public/v1, and on that host only /public/v1 answers.

The full checklist for a 401 is in Authentication. To tell whether the problem is yours or ours, see API status.

What to have at hand

Item	Where to find it
request_id of the call	The Request-Id response header, or the request_id field of the error
Date and time, with zone	Your log, or the date column under View usage
Method and path	GET /public/v1/me, for instance
HTTP status and the code	The response
Visible prefix of the key	The first 14 characters, on the key screen or in key.prefix
What you expected	You

If the problem is intermittent, say how many calls failed out of how many, and over what period.

The request_id is the most useful item on the list: it is what locates the call with no guesswork.

Never send the key. The prefix is enough for us to know which one it is.

What support cannot do

• Read your key. The server stores only a hash. A lost key is not recovered: rotate it or create another one.
• Create, rotate or revoke a key for you. That is the OWNER or ADMIN in the panel, with the password.
• Manage keys through the API itself. There is no key management route: keys are created, edited, rotated and revoked in the panel.
• See a call older than 30 days. The usage log keeps 30 days.
• See a call the API did not recognise. A token that belongs to no key leaves no line in the log, because there is nobody to attribute the attempt to.

A question that is not about the API

Plan, billing, a panel screen or a product feature: use Help, in the panel menu. The product support channel is there.

A security flaw has its own path: Report a vulnerability.

Next step

• API status: whose problem it is, response by response.
• Errors: the whole catalogue, with what to do for each code.
• Report a vulnerability: when what you found is a security problem.