Call v2 là gì
Project Playtime Call V2 là một ứng dụng Chiến thuật được phát triển bởi awesome work. Trên trang này tải xuống Phiên bản máy tính Project Playtime Call V2 chạy trên máy tính bằng cách cài đặt trình giả lập Android. Trình giả lập Android là phần mềm mô phỏng hệ thống điện thoại di động Android trên hệ điều hành máy tính, LDPlayer là trình giả lập Android chạy trên máy tính WINDOWS. Bằng cách mô phỏng môi trường hoạt động của điện thoại di động Android 9.0, LDPlayer có các chức năng mà trên điện thoại di động không có ,chẳng hạn như đa cửa sổ, lệnh macro và ghi lại thao tác vv , để có thể chơi mượt mà các game di động trên máy tính. Nó là một trình giả lập Android được thiết kế đặc biệt cho những người đam mê trò chơi.
The Amplitude Developers Postman profile has a full library of example requests and responses for this API. Show
Check out the Amplitude Developers Profile to view the collection. You don't need a Postman account to browse. If you already use Postman, you can . AuthorizationThis API doesn't use authorization, but uses your API key. Pass your API key in the body of the request like 4.See Find your Amplitude Project API Credentials for help locating your credentials. EndpointsRegionEndpointStandard Serverhttps://api2.amplitude.com/2/httpapiEU Residency Serverhttps://api.eu.amplitude.com/2/httpapiConsiderationsUpload limitFor Starter plan customers: Limit your upload to 100 batches per second and 1000 events per second. You can batch events into an upload, but don't send more than 10 events per batch. Amplitude expects fewer than 100 batches per second, and the 1000 events per second limit still applies. For customers on Growth and Enterprise plans: Contact Support if you need to send more than 1000 events per second. There is no hard limit on the Enterprise plan, but devices that exceed 30 events per second are throttled. Keep request sizes under 1 MB with fewer than 2000 events per request. When you exceed these size limits, you get a 413 error. If you have high volume and concerned with scale, partition your work based on 5 or 6. This ensures that throttling on a particular 5 (or 6) doesn't impact all senders in your system. If you are using a proxy service to send events to Amplitude, make sure that throttling is forwarded to your clients, instead of letting spammy clients slow down a partition of work in your system.Information for partner integrationsIf you have an event ingestion integration with Amplitude, you need to send your integration's assigned partner ID in the event payload. For help finding your integration's partner ID and a payload example, see . All-zero device IDs: Limit Ad Tracking enabledAs of iOS 10, Apple replaces the Identifier for Advertiser (IDFA) with all zeros if the user enables Limit Ad Tracking. Because all events require a device ID, Amplitude drops device IDs of all zeros and returns an error on the request. If you are passing the IDFA as the device ID, first run a check on the IDFA value. If it's all zeros, pass a different value for the device ID, such as the Identifier for Vendor (IDFV). Windows OSIf you are using a Windows operating system, then you may have to replace all single quotes with escaped double quotes. String character limitAll string values, like 6, event, or user property values, have a character limit of 1024 characters.Set date valuesAmplitude compares dates as strings, so it's best to use the ISO 8601 format ( 0). This format lets you perform date comparisons, (for example: 1). Comparison also works for datetime values in this format (for example: 2).Set time valuesYou must send the 3 parameter in each event as millisecond since epoch. Any other format (such as ISO format) results in a 400 Bad Request response.Event deduplicationIt's highly recommended that you send an 4 for each event to prevent sending duplicate events to Amplitude. Amplitude ignores subsequent events sent with the same 4 on the same 5 (if the event has a 5 value) in each app within the past 7 days.Device IDs and User IDs minimum lengthDevice IDs and User IDs must be strings with a length of 5 characters or more. This is to prevent potential instrumentation issues. If an event contains a device ID or user ID that's too short, the ID value is removed from the event. Override the default minimum length of 5 character by passing the 8 option with the request.If the event doesn't have a 6 or 5 value, the upload may be rejected with a 400 status.Invalid IDsThese IDs are invalid, and result in a 400 error:
Upload requestSend a POST request to 1Example requestcURLHTTPJavaScriptNodeJsRubyPythonJavaGo
Upload request body parametersNameDescription 2Required. String. Amplitude project API key.Required. []. Array of to upload.Optional. []. Object.Example upload request body
Keys for the event argumentYou can send these keys in the JSON event object. Note that one of 6 or 5 is required, as well as the 7.Name Description 6Required if 5 isn't used. String. ID for the user. Must have a minimum length of 5 characters unless overridden with the 0 option. 5Required if 6 isn't used. String. A device-specific identifier, such as the Identifier for Vendor on iOS. If a 5 isn't sent with the event, then it's set to a hashed version of the 6. 7Required. String. A unique identifier for your event. The following event names are reserved for Amplitude use: 6 Start Session", 6 End Session", 6 Revenue", 6 Revenue (Verified)", 6 Revenue (Unverified)", and 6 Merged User". 3Optional. The timestamp of the event in milliseconds since epoch. If time isn't sent with the event, then it's set to the request upload time. 3Optional. Object. A dictionary of key-value pairs that represent data to send along with the event. You can store property values in an array. Date values are transformed into string values. Object depth may not exceed 40 layers. 4Optional. Object. A dictionary of key-value pairs that represent data tied to the user. You can store property values in an array. Date values are transformed into string values. Object depth may not exceed 40 layers. 5Optional. Object. This feature is only available to Enterprise customers who have purchased the Accounts add-on. This field adds a dictionary of key-value pairs that represent groups of users to the event as an event-level group. You can track up to 5 unique group types and 10 total group values per event. Any groups past that threshold aren't tracked. 6Optional. Boolean. When 7 user properties aren't synced. Defaults to 8. See for more information. 9Optional. String. The current version of your application. 0Optional. String. Platform of the device. 1Optional. String. The name of the mobile operating system or browser that the user is using. 2Optional. String. The version of the mobile operating system or browser the user is using. 3Optional. String. The device brand that the user is using. 4Optional. String. The device manufacturer that the user is using. 5Optional. String. The device model that the user is using. 6Optional. String. The carrier that the user is using. 7Optional. String. The current country of the user. 8Optional. String. The current region of the user. 9Optional. String. The current city of the user. 0 Optional. String. The current Designated Market Area of the user. 1Optional. String. The language set by the user. 2Optional. Float. The price of the item purchased. Required for revenue data if the revenue field isn't sent. You can use negative values for refunds. 3Optional. Integer. The quantity of the item purchased. Defaults to 1 if not specified. 4Optional. Float. Revenue = (price x quantity). If you send all 3 fields of price, quantity, and revenue, then the revenue value is (price x quantity). Use negative values for refunds. 5Optional. String. An identifier for the item purchased. You must send a price and quantity or revenue with this field. 6Optional. String. The type of revenue for the item purchased. You must send a price and quantity or revenue with this field. 7Optional. Float. The current Latitude of the user. 8Optional. Float. The current Longitude of the user. 9Optional. String. The IP address of the user. Use 0 to use the IP address on the upload request. Amplitude uses the IP address to reverse lookup a user's location (city, country, region, and DMA). Amplitude can drop the location and IP address from events after they reach Amplitude servers. Contact the Support team to configure this. 1Optional. String. (iOS) Identifier for Advertiser. 2Optional. String. (iOS) Identifier for Vendor. 3Optional. String. (Android) Google Play Services advertising ID 4Optional. String. (Android) Android ID (not the advertising ID) 5Optional. Integer. (Optional) An incrementing counter to distinguish events with the same 6 and timestamp from each other. Amplitude recommends you send an 5, increasing over time, especially if you expect events to occur simultaneously. 8Optional. Long. The start time of the session in milliseconds since epoch (Unix Timestamp), necessary if you want to associate events with a particular system. A 8 of -1 is the same as no 8 specified. 4Optional. String. A unique identifier for the event. Amplitude deduplicates subsequent events sent with the same 5 and 4 within the past 7 days. Amplitude recommends generating a UUID or using some combination of 5, 6, 7, 5, and time. 8Optional. Object. Tracking plan properties. Amplitude supports only branch, source, version properties. 9Optional. String. The tracking plan branch name. For example: "main". 00Optional. String. The tracking plan source. For example: "web". 01Optional. String. The tracking plan version. For example: "1", "15".OptionsName Description 8Optional. Integer. Overrides the default minimum length of 5 for 6 & 5 fields.Response formatIt's best practice to implement retry logic and send an 4 (used for deduplication of the same event) in your events. This prevents lost events or duplicated events if the API is unavailable or a request fails.200 response SuccessSummary: Successful real time event upload. If you don't receive a 06 response, retry your request.
PropertiesName Description 07Integer. 200 success code 08Integer. The number of events ingested from the upload request. 09Integer. The size of the upload request payload in bytes. 10Long. The time in milliseconds since epoch (Unix Timestamp) that Amplitude's event servers accepted the upload request.400 response InvalidRequestError. A 400 indicates invalid upload request. Check the response for more information. Possible reasons for an invalid request:
Invalid fields exampleSilenced devices example 0 1Properties (invalid or missing JSON)Name Description 07Integer. 400 error code 11String. Error description. Possible values are 16, 17, 18, 19, 20, 21, 22 23String. Indicates which request-level required field is missing. 13Object. A map from field names to an array of indexes into the events array indicating which events have invalid values for those fields 25Object. A map from field names to an array of indexes into the events array indicating which events are missing those required fieldsProperties (SilencedDeviceID)Name Description 07Integer. 400 error code 11String. Error description. 28Integer. Your app's current events per second threshold. If you exceed this rate your requests are throttled. 29Object. A map from device_id to its current number of daily events, for all devices that exceed the app's daily event quota. 30[string]. Array of 5s that Amplitude has silenced. 32[integer]. Array of indexes in the events array indicating events whose device_id got silenced. 33Object. A map from device_id to its current events per second rate, for all devices that exceed the app's current threshold. 34[integer]. Array of indexes in the events array indicating events whose 6 or 5 got throttled413 response PayloadTooLargeError. The payload size is too big (request size exceeds 1MB). Split your events array payload into multiple requests and try again. 2PropertiesNameDescription 07Integer. 413 error code 11String. Error description.429 response TooManyRequestsForDeviceError. Too many requests for a user or device. Amplitude throttles requests for users and devices that exceed 30 events per second (measured as an average over a recent time window). You should pause sending events for that user or device for a period of 30 seconds before retrying and continue retrying until you no longer receive a 429 response. 3PropertiesName Description 07Integer. 429 error code 11String. Error description. 28Integer. Your app's current events per second threshold. If you exceed this rate your requests are throttled. 33Object. A map from 5 to its current events per second rate, for all devices that exceed the app's current threshold. 44Object. A map from 6 to their current events per second rate, for all users that exceed the app's current threshold. 34Array of indexes in the events array indicating events whose 6 or 5 were throttled.Server Error 500, 502, 504500, 502, and 504 . Amplitude encountered an error while handling the request. A request with this response may not have been accepted by Amplitude. If you retry the request, it could duplicate the events. To avoid duplication, send an 4 in your requests.503 Service Unavailable. Request failed because of an internal Amplitude issue. Retrying a request with a 50 response doesn't risk duplicating events.
|