Contact

What to include so the first reply is useful

Most of the back and forth on a support thread is us asking which call you made. Sending that up front removes a round trip.

• •The endpoint path you called, for example /twitter/user/tweets, and the parameters you sent.
• •Roughly when you called it, in UTC. A time window is enough to find the request.
• •The email on the account, so the request can be matched to your usage.
• •What you expected back and what actually came back, pasted rather than described.
• •Never paste the API key itself. The first few characters are enough to identify which key you are on.

Where the answer may already be

Four questions arrive more often than the rest, and each has a page that answers it without waiting for a reply.

• •Is something down right now: the status page.
• •What a given call costs: pricing and the cost calculator.
• •How an endpoint behaves and what it returns: the documentation and rate limits.
• •The questions developers ask before they build: the answers index, and the changelog for what moved.

Sales, billing and account questions

Billing is per call with no subscription and no seat count, so there is no plan to negotiate before you start. Standard reads bill at $0.0008 per call and 24 of the 109 endpoints are free, and signup carries $0.50 in credit with no card, which is enough calls to answer most pricing questions by running them. Write in when the question is about an invoice, a specific account, or volume beyond what the published rates cover, and include the account email.

Security and abuse reports

Send security reports to the same address with the word security in the subject line so they are read first. Our handling of credentials and customer data is written up on security and trust and data handling. Abuse reports about how the API is being used go to the same address.