This is calculated with cost = 30 * 10 * 6. Filters on events don't count in this section. This configuration generates a cost of 10 because in has one segment (by Any Users, cost of one), one condition (Language = English, cost of one), and two group by values (Country and Platform, cost of four each) applied.
#POSTMAN TUTORIAL W3SCHOOLS PLUS#
Number of conditions: This is the number of segments plus the number of conditions within the segments applied to the chart you are looking at.Number of days: This is the number of days in the query.Here is how Amplitude determines each variable in the formula: Amplitude calculates cost based on this formula:Ĭost = (# of days) * (# of conditions) * (cost for the query type) All other endpoints ¶Īll other endpoints use cost per query model. The User Activity and User Search endpoints have a different rate limit than all other request types. You can run up to 360 queries per hour for user activity and user search endpoints. These limits are per project, and the 429 error also includes information on how you are exceeding the limit.Ĭoncurrent Limit: You can run up to 5 concurrent requests across all Amplitude REST API endpoints, including cohort download. Exceeding these limits returns a 429 error. The rate limit restricts the total number of queries you can run per hour. The concurrent limit restricts the number of requests you can run at the same time. The Dashboard REST API time zone is the same as your Amplitude project's time zone.įor each endpoint, there is a concurrent limit and a rate limit.If you aren't using cURL, then don't encode your request with backslash escape characters. Some examples in this article use backslash syntax to escape characters when using cURL.For example, encode Play Song as Play%20Song. Use the W3Schools encoding reference for help. You may have to URL encode special characters in the names of event types, event properties, and user properties.See Find your Amplitude Project API Credentials for help locating your credentials. header 'Authorization: Basic YWhhbWwsdG9uQGFwaWdlZS5jb206bClwYXNzdzByZAo' Your authorization header should look something like this: api-key replaces username, and secret-key replaces the password. Pass base64-encoded credentials in the request header like. This API uses basic authentication, using the API key and secret key for your project. If you already use Postman, you can fork and run the collection in Postman. You don't need a Postman account to browse. The Amplitude Developers Postman profile has a collection of the example requests included in this documentation, including detailed responses for each call. Advanced session length distribution examples
0 kommentar(er)
