UPLOAD_AUDIENCE_GROUP_INVALID_AUDIENCE_ID_FORMAT You can't create an audience for a message (request ID) that was sent over 60 days (5,184,000 seconds) ago. The specified request ID is incorrect or LINE not ready to create an audience with the specified request ID. There is already an audience with the specified request ID. The audience's name contains an invalid character (such as \n or some other control character). You have already created the maximum number of audiences (1,000). This audience can't be used because it's been more than 180 days (15,552,000 seconds) since this audience was created. MessageĪUDIENCE_GROUP_CAN_NOT_UPLOAD_STATUS_EXPIRED The details of the error that are found in the ssage property of the JSON error responses are shown below. You have exceeded the target limit for additional messages. For more information, see Do I get an error when I send a message with a user ID that doesn't exist? in FAQ. One reason this may appear is if the user ID specified does not exist. The reason is displayed for "XXX".Īccess to this API is not available for your accountĪppears when calling an API that you do not have permission to use.Īppears when the message fails to be sent. The specific line and column are displayed.Ī content type not supported by the API is requested.Īuthentication failed due to the following reason: XXXĪuthentication failed when the API was called. The JSON in the request body could not be parsed. The request body could not be parsed as JSON (line: XXX, column: XXX) The specific property is displayed for "XXX". The property, XXX, in the request body is invalid (line: XXX, column: XXX)Īn invalid property was specified in the request body. Sent a reply message using a used reply token.Sent a reply message using a reply token that became invalid once a certain period of time had passed after receiving a message.The reply token specified in replyToken to Send reply message is invalid. Further details are shown in the ssage and details.property properties. The number of errors is displayed for "X". MessageĪn error was found in the JSON data of the request body. The main error messages that are found in the message property of the JSON error responses are shown below. If the request has already been accepted using the same retry key, the x-line-request-id of the accepted request is shown. A unique ID is generated for each request The following HTTP headers are included in Messaging API responses. You can check the limit (opens new window) for your account in the LINE Official Account Manager. Exceeded the Limit on the number of concurrent operations for requests.Media type of the uploaded file is unsupported. Make the request smaller than 2MB and try again. For details, see Retry failed API request. A user hasn't consented to their profile information being obtainedįor more information, see Consent on getting user profile information in the Messaging API documentation.Īn API request with the same retry key has already been accepted.A user blocked the target LINE Official Account after adding it as a friend.A user hasn't added the target LINE Official Account as a friend.Confirm that your account or plan is authorized to access the resource. Valid channel access token is not specified.
SEND CODE
We follow the HTTP status code specification (opens new window) unless otherwise stated. These HTTP status codes are returned after an API call. If the status of a job ( jobs.jobStatus property) is waiting to run ( QUEUED) or running ( WORKING), it will be counted as an operation. You can check the number of requests being processed with the jobs property of the following endpoint response. If you've received an error, wait a while before making a request again. Requests that exceed the limit on the number of concurrent operations will return an error with status code 429 Too Many Requests. The total number of requests processed concurrently by the following endpoints is counted as the number of concurrent operations. We have set a limit on the number of concurrent endpoint operations per audience ID ( audienceGroupId), for creating an audience for uploading user IDs and adding user IDs to an audience. # Limit on the number of concurrent operations Change the authority level of the audience.Get the authority level of the audience.Create audience for impression-based retargeting.Create audience for click-based retargeting.Add user IDs or Identifiers for Advertisers (IFAs) to an audience for uploading user IDs (by file).Add user IDs or Identifiers for Advertisers (IFAs) to an audience for uploading user IDs (by JSON).Create audience for uploading user IDs (by file).Create audience for uploading user IDs (by JSON).When developing a LINE Bot using the Messaging API, follow the Development guidelines, including the guidelines on rate limits. If you send requests exceeding the rate limit, you will receive an error message saying, 429 Too Many Requests.
0 kommentar(er)
