Drıftstack docs
Docs

Cannot create an API key until the owner accepts updated legal terms

You might be here because: “409 legal acceptance required when creating a key” · “Operation requires acceptance of N document(s) before proceeding” · “can’t create an API key, something about terms” · “review and accept the required terms before continuing” · “I’m an admin and accepted the terms but still can’t create a key”

Short answer

Creating an API key, or rotating one (which replaces it with a new key), is blocked (HTTP 409 legal-acceptance-required) while the account owner has not accepted a new version of one or more legal documents that needs acceptance, or a document it never accepted. A wording or formatting edit that keeps a document’s version number blocks nothing and asks for nothing. The response lists the pending documents. The owner accepts them from the banner at the top of the dashboard; then key creation works.

Check first

  • Is there a banner listing documents with Accept all and continue at the top of the dashboard?
  • Are you a team admin? It is the owner’s acceptance that counts, not yours. Ask the owner to sign in and accept.
  • Is the message actually a plan gate (“API keys aren’t included…”)? Different doc — see Related.

Likely causes and fixes

  1. Owner has not accepted an updated document. Terms, Privacy Policy, DPA or AUP got a new version that needs acceptance. The owner: dashboard → banner → review each linked document → Accept all and continue → the page reloads and the banner disappears. Then create the key.

  2. Creating via the API / SDK, got a 409 with pending_acceptances. Same cause. The body names each document_key and current_version. Have the owner accept in the dashboard, then retry.

  3. An app connected with OAuth gets a 409 when it asks for its access token. Same cause: the access token is a new API key, so it waits for acceptance by the account that approved the app (for a team member, that is your own account, not the team owner’s), and the body carries error: invalid_grant beside pending_acceptances. That account accepts in the dashboard; the app then retries (within 5 minutes of the approval; after that the app starts the authorization again).

  4. Banner errors while accepting (“Could not check…”, “Acceptance outcome is unknown…”, “N accepted; M still require acceptance”) are covered in Review and accept updated Terms / Privacy / DPA / AUP.

If it still fails

Press Talk to a person in this chat (or open Help) and include: owner account email, the pending document keys shown, and whether the banner appears for the owner. Legal questions about the documents’ content go to a person; the AI does not interpret the terms.