--- title: Media API description: "The **Media API** lets you create, upload, and retrieve media files for eBay listings, including the following resources: * images * videos * documents for Regulatory requirements * post\\_order documents for post-order activities (such as returns) Images are uploaded to eBay Picture Services (EPS) and can then be used in listings. Since published listings require at least one picture, image support is a core part of the API. Videos can also be uploaded and associated with listings, giving buyers a better view of an item's condition, features, and usage. For larger files, the API supports a staged upload flow and resumable upload capabilities. The **Media API** also supports document upload for listing attachments such as user guides, product safety information, and other compliance-related documents, including files used for GPSR requirements and post-order documents. Once uploaded, these media assets can be referenced in listings through other eBay APIs, helping sellers create richer, more informative, and more compliant listings. **Note:** To learn more about using this API, see [Managing images](https://developer.ebay.com/api-docs/sell/static/inventory/managing-image-media.html), [Managing videos](https://developer.ebay.com/api-docs/sell/static/inventory/managing-video-media.html), and [Managing documents](https://developer.ebay.com/api-docs/sell/static/inventory/managing-document-media.html)." api_version: 1.0 api_name: media_api api_type: REST api_group: sell/media_api source_url: html: https://developer.ebay.com/develop/api/sell/media_api md: https://developer.ebay.com/develop/api/sell/media_api.md --- # Media API API The **Media API** lets you create, upload, and retrieve media files for eBay listings, including the following resources: * images * videos * documents for Regulatory requirements * post\_order documents for post-order activities (such as returns) Images are uploaded to eBay Picture Services (EPS) and can then be used in listings. Since published listings require at least one picture, image support is a core part of the API. Videos can also be uploaded and associated with listings, giving buyers a better view of an item's condition, features, and usage. For larger files, the API supports a staged upload flow and resumable upload capabilities. The **Media API** also supports document upload for listing attachments such as user guides, product safety information, and other compliance-related documents, including files used for GPSR requirements and post-order documents. Once uploaded, these media assets can be referenced in listings through other eBay APIs, helping sellers create richer, more informative, and more compliant listings. **Note:** To learn more about using this API, see [Managing images](https://developer.ebay.com/api-docs/sell/static/inventory/managing-image-media.html), [Managing videos](https://developer.ebay.com/api-docs/sell/static/inventory/managing-video-media.html), and [Managing documents](https://developer.ebay.com/api-docs/sell/static/inventory/managing-document-media.html). ## API Methods The following API methods are available: ### createImageFromFile #### POST /image/create_image_from_file **Description:** This method uploads a picture file to eBay Picture Services (EPS) using multipart/form-data. All images must comply with eBay's picture requirements, such as dimension and file size restrictions. For more information, see [Picture policy](https://www.ebay.com/help/policies/listing-policies/picture-policy?id=4370). The image formats supported are **JPG**, **GIF**, **PNG**, **BMP**, **TIFF**, **AVIF**, **HEIC**, and **WEBP**. For more information, see [Image requirements](/api-docs/sell/static/inventory/managing-image-media.html#image-requirements). **Note:** Animated GIF, and multi-page PNG/TIFF files, are not supported. Any animation effect of supported formats will be lost upon upload. This call does not have a JSON Request payload but uploads the file as form-data. For example: image: "sample\_picture.jpg" See **Samples** for information. **Note:** You must use a **Content-Type** header with its value set to 'multipart/form-data'. When an EPS image is successfully created, the method returns the HTTP Status Code `201 Created`. The method also returns the getImage URI in the **Location** response header. **Important!** Make sure to capture the image ID URI returned in the response [Location header](/develop/guides-v2/using-ebay-restful-apis#responseheaders) provided in the following format: `https://apim.ebay.com/commerce/media/v1_beta/image/_{image_id}_` You can capture the entire URI, or just save the `{image_id}` only. Pass the `{image_id}` as a path parameter in the **[getImage](/develop/api/sell/media_api#sell-media_api-image-getimage)** method to return the value needed to associate an image to a listing using the Trading and Inventory APIs. See [Managing images](/api-docs/sell/static/inventory/managing-image-media.html) for additional details. **Important!**All POST methods in the Media API, including this method, are subject to short-duration rate limits at the user level: 50 requests per 5 seconds. **Parameters:** - **Content-Type** (string) *required* - This header indicates the format of the request body provided by the client. Its value should be set to **multipart/form-data**. For more information, refer to [HTTP request headers](/api-docs/static/rest-request-components.html#HTTP). ### createImageFromUrl #### POST /image/create_image_from_url **Description:** This method uploads a picture to eBay Picture Services (EPS) from the specified URL. Specify the location of the picture on an external web server through the **imageUrl** field. All images must comply with eBay’s picture requirements, such as dimension and file size restrictions. For more information, see [Picture policy](https://www.ebay.com/help/policies/listing-policies/picture-policy?id=4370). The image formats supported are **JPG**, **GIF**, **PNG**, **BMP**, **TIFF**, **AVIF**, **HEIC**, and **WEBP**. In addition, the provided URL must be secured using HTTPS (HTTP is not permitted). For more information, see [Image requirements](/api-docs/sell/static/inventory/managing-image-media.html#image-requirements). **Note:** Animated GIF, and multi-page PNG/TIFF files, are not supported. Any animation effect of supported formats will be lost upon upload. When an EPS image is successfully created, the method returns the HTTP Status Code `201 Created`. The method also returns the getImage URI in the **Location** response header. **Important!** Make sure to capture the image ID URI returned in the response [Location header](/develop/guides-v2/using-ebay-restful-apis#responseheaders) provided in the following format: `https://apim.ebay.com/commerce/media/v1_beta/image/_{image_id}_` You can capture the entire URI, or just save the `{image_id}` only. Pass the `{image_id}` as a path parameter in the **[getImage](/develop/api/sell/media_api#sell-media_api-image-getimage)** method to return the value needed to associate an image to a listing using the Trading and Inventory APIs. See [Managing images](/api-docs/sell/static/inventory/managing-image-media.html) for additional details. **Important!**All POST methods in the Media API, including this method, are subject to short-duration rate limits at the user level: 50 requests per 5 seconds. **Parameters:** - **Content-Type** (string) *required* - This header indicates the format of the request body provided by the client. Its value should be set to **application/json**. For more information, refer to [HTTP request headers](/api-docs/static/rest-request-components.html#HTTP). ### getImage #### GET /image/{image_id} **Description:** This method retrieves an EPS image URL and its expiration details for the unique identifier specified in the path parameter **image\_id**. Use the retrieved EPS image URL to add the image to a listing through the **Inventory API** or the **Trading API**. See [Managing images](/api-docs/sell/static/inventory/managing-image-media.html) for additional details. **Note:** If a user inputs a valid **image\_id** as a path parameter but the EPS image associated with that ID has expired, the call will fail and a **404 Not Found** status code will be returned. **Parameters:** - **image_id** (string) *required* - This path parameter is the unique identifier of a created image. Use the value returned in the location header of the method used to create the image (**createImageFromFile** or **createImageFromUrl**, as applicable). ### createVideo #### POST /video **Description:** This method creates a video resource. When using this method, specify the **title**, **size**, and **classification** of the video resource to be created. **Description** is an optional field for this method. **Tip:** See [Adding a video to your listing](https://www.ebay.com/help/selling/listings/creating-managing-listings/add-video-to-listing?id=5272#section3) in the eBay Seller Center for details about video formatting requirements and restrictions, or visit the relevant eBay site help pages for the region in which the listings will be posted. When a video resource is successfully created, the method returns the HTTP Status Code `201 Created.`The method also returns the location response header containing the **video ID**, which you can use to retrieve the video. **Note:** There is no ability to edit metadata on videos at this time. There is also no method to delete videos. To upload a created video to a created video resource, use the [uploadVideo](/develop/api/sell/media_api#sell-media_api-video-uploadvideo) method. **Important!**All POST methods in the Media API, including this method, are subject to short-duration rate limits at the user level: 50 requests per 5 seconds. **Parameters:** - **Content-Type** (string) *required* - This header indicates the format of the request body provided by the client. Its value should be set to **application/json**. For more information, refer to [HTTP request headers](/api-docs/static/rest-request-components.html#HTTP). ### getVideo #### GET /video/{video_id} **Description:** This method retrieves a video's metadata and content given a specified **video ID**. The method returns the **title**, **size**, **classification**, **description**, **video ID**, **playList**, **status**, **status message** (if any), **expiration date**, and **thumbnail** image of the retrieved video. The video's **title**, **size**, **classification**, and **description** are set using the [createVideo](/develop/api/sell/media_api#sell-media_api-video-createvideo) method. The video's **playList** contains two URLs that link to instances of the streaming video based on the supported protocol. The **status** field contains the current status of the video. After a video upload is successfully completed, the video's **status** will show as `PROCESSING` until the video reaches one of the terminal states of `LIVE`, `BLOCKED` or `PROCESSING_FAILED`. If a video's processing fails, it could be because the file is corrupted, is too large, or its size doesn't match what was provided in the metadata. Refer to the error messages to determine the cause of the video's failure to upload. The **status message** will indicate why a video was blocked from uploading. If a video is not being used on an active listing, its **expiration date** is automatically set to 30 days after the video's initial upload. The video's **thumbnail** image is automatically generated when the video is created. **Parameters:** - **video_id** (string) *required* - The unique identifier of the video to be retrieved. ### uploadVideo #### POST /video/{video_id}/upload **Description:** This method associates the specified file with the specified **video ID** and uploads the input file. After the file has been uploaded the processing of the file begins. **Note:** The size of the video to be uploaded must exactly match the size of the video's input stream that was set in the [createVideo](/develop/api/sell/media_api#method-video-createVideo) method. If the sizes do not match, the video will not upload successfully. When a video is successfully uploaded, it returns the HTTP Status Code `200 OK`. The status flow is `PENDING_UPLOAD` > `PROCESSING` > `LIVE`, `PROCESSING_FAILED`, or `BLOCKED`. After a video upload is successfully completed, the status will show as `PROCESSING` until the video reaches one of the terminal states of `LIVE`, `BLOCKED`, or `PROCESSING_FAILED`. If the size information (in bytes) provided is incorrect, the API will throw an error. **Tip:** See [Adding a video to your listing](https://www.ebay.com/help/selling/listings/creating-managing-listings/add-video-to-listing?id=5272#section3) in the eBay Seller Center for details about video formatting requirements and restrictions, or visit the relevant eBay site help pages for the region in which the listings will be posted. To retrieve an uploaded video, use the [getVideo](/api-docs/commerce/media/resources/video/methods/getVideo) method. **Important!**All POST methods in the Media API, including this method, are subject to short-duration rate limits at the user level: 50 requests per 5 seconds. **Parameters:** - **Content-Length** (string) - Use this header to specify the content length for the upload. Use Content-Range: bytes {1}-{2}/{3} and Content-Length:{4} headers. **Note:** This header is optional and is only required for _resumable_ uploads (when an upload is interrupted and must be resumed from a certain point). - **Content-Range** (string) - Use this header to specify the content range for the upload. The Content-Range should be of the following bytes ((?:\[0-9\]+-\[0-9\]+)|\\\\\\\\\*)/(\[0-9\]+|\\\\\\\\\*) pattern. **Note:** This header is optional and is only required for _resumable_ uploads (when an upload is interrupted and must be resumed from a certain point). - **Content-Type** (string) *required* - Use this header to specify the content type for the upload. The Content-Type should be set to `application/octet-stream`. - **video_id** (string) *required* - The unique identifier of the video to be uploaded. ### createDocument #### POST /document **Description:** This method stages a document to be uploaded, and requires the type of document to be uploaded, and the language(s) that the document contains. A successful call returns a **documentId** value that is then used as a path parameter in an [uploadDocument](< /develop/api/sell/media_api#sell-media_api-document-uploaddocument>) call. When a document is successfully created, the method returns the HTTP Status Code `201 Created.` The method returns **documentId** in the response payload, which you can use to retrieve the document resource. This ID is also returned in the **location** header, for convenience. **Important!** Make sure to capture the document ID value returned in the response payload. This value is required to use the other methods in the **document** resource, and also needed to associate a document to a listing using the Trading and Inventory APIs. To upload a created document, use the document ID returned from this method's response with the [uploadDocument](< /develop/api/sell/media_api#sell-media_api-document-uploaddocument>) method. See [Managing documents](/api-docs/sell/static/inventory/managing-document-media.html) for information on creating, uploading, and adding documents to listings. **Important!**All POST methods in the Media API, including this method, are subject to short-duration rate limits at the user level: 50 requests per 5 seconds. **Parameters:** - **Content-Type** (string) *required* - This header indicates the format of the request body provided by the client. Its value should be set to **application/json**. For more information, refer to [HTTP request headers](/api-docs/static/rest-request-components.html#HTTP). ### createDocumentFromUrl #### POST /document/create_document_from_url **Description:** This method downloads a document from the provided URL and adds that document to the user's account. This method requires the URL of the document, the type of document to be uploaded, and the language(s) that the document contains. When a document is successfully created, the method returns the HTTP Status Code `201 Created.` The method returns **documentId** in the response payload, which you can use to retrieve the document resource. This ID is also returned in the **location** header, for convenience. **Important!** Make sure to capture the document ID value returned in the response payload. This value is required to use the other methods in the **document** resource, and also needed to associate a document to a listing using the Trading and Inventory APIs. After creating a document using this method, a [getDocument](/develop/api/sell/media_api#sell-media_api-document-getdocument) call should be made to check for a **documentStatus** of `ACCEPTED`. Only documents with this status can be added to a listing. See [Managing documents](/api-docs/sell/static/inventory/managing-document-media.html) for more information on creating, uploading, and adding documents to listings. **Important!**All POST methods in the Media API, including this method, are subject to short-duration rate limits at the user level: 50 requests per 5 seconds. **Parameters:** - **Content-Type** (string) *required* - This header indicates the format of the request body provided by the client. Its value should be set to **application/json**. For more information, refer to [HTTP request headers](/api-docs/static/rest-request-components.html#HTTP). ### getDocument #### GET /document/{document_id} **Description:** This method retrieves the current **status** and metadata of the specified document. **Important!** The document ID value returned in the response payload of the [createDocument](/develop/api/sell/media_api#sell-media_api-document-createdocument) or the [createDocumentFromUrl](/develop/api/sell/media_api#sell-media_api-document-createdocumentfromurl) method is a required input path parameter for this method. See [Managing documents](/api-docs/sell/static/inventory/managing-document-media.html) for additional information. **Parameters:** - **document_id** (string) *required* - The unique identifier of the document for which status and metadata is being retrieved. This value is returned in the response of the [createDocument](/develop/api/sell/media_api#method-document-createdocument) or [createDocumentFromUrl](/develop/api/sell/media_api#method-document-createdocumentfromurl) method used to create the document. ### uploadDocument #### POST /document/{document_id}/upload **Description:** This method associates the specified file with the specified document ID and uploads the input file. After the file has been uploaded, the processing of the file begins. Supported file types include .PDF, .JPEG/.JPG, and .PNG, with a maximum file size of 10 MB (10485760 bytes). **Note:** Animated and multi-page PNG files are not currently supported. **Note:** The document ID value returned in the response of the [createDocument](/develop/api/sell/media_api#sell-media_api-document-createdocument) method is a required input path parameter for this method. This value is also returned in the **location** header of the **createDocument** response payload. A successful upload returns the HTTP Status Code `200 OK`. See [Managing documents](/api-docs/sell/static/inventory/managing-document-media.html) for additional information. **Note:** You must use a **Content-Type** header with its value set to **multipart/form-data**. This call does not have a JSON Request payload but uploads the file as form-data. For example: file: @"/C:/Users/.../drone\_user\_warranty.pdf" See [Samples](/develop/api/sell/media_api#sell-media_api-document-uploadDocument#h2-samples) for information. **Important!**All POST methods in the Media API, including this method, are subject to short-duration rate limits at the user level: 50 requests per 5 seconds. **Parameters:** - **document_id** (string) *required* - The unique identifier of the document to be uploaded. This value is returned in the response of the [createDocument](/develop/api/sell/media_api#sell-media_api-document-createdocument) method. - **Content-Type** (string) *required* - This header indicates the format of the request body provided by the client. Its value should be set to **multipart/form-data**. For more information, refer to [HTTP request headers](/api-docs/static/rest-request-components.html#HTTP). ### uploadPostOrderDocument #### POST /post_order/document **Description:** This method uploads a document for post‑order processes (for example, a seller providing a return shipping label). Supported file types include .PDF, .JPEG/.JPG, .BMP, .GIF and .PNG, with a maximum file size of 5 MB (5,242,880 bytes). **Note:** This method is currently restricted and requires a special **OAuth scope** not available to all users. **Note:** Animated and multi-page PNG files are not currently supported. For multi-page content, use PDF. The maximum number of pages allowed varies by the **documentUsageType**. Send a multipart/form‑data request with: * **file**: the document file, set `key: file` * **documentUsageType**: for example, `RETURN_SHIPPING_LABEL` * **entityType**: for example, `RETURNS` * **entityId**: the unique identifier for the post-order entity A successful call returns the HTTP Status Code **201 Created** with the document ID in the **Location header** (no response body is returned). The document’s initial state is **SUBMITTED**. When its identifier is associated with a post-order entity through an eBay GraphQL mutation, the state changes to **PUBLISHED**. **Note:** A post-order entity is part of eBay's order management for activities after purchase (such as returns). **Important!** * Capture and retain the **documentId** in the response's [Location header](/develop/guides-v2/using-ebay-restful-apis#responseheaders). It is required to use the other **post\_order** methods and to associate the document with a post-order entity. The location response header contains the URI of the newly created document ID in the format: `https://apiz.ebay.com/commerce/media/v1_beta/post_order/document/{documentId}` * All documents (published or submitted) expire and become inaccessible after their expiration date. * All **POST** methods in the **Media API**, including this method, are subject to short-duration, user-level rate limits: 50 requests per 5 seconds. **Parameters:** - **Content-Type** (string) *required* - This header indicates the format of the request body provided by the client. Its value should be set to **multipart/form-data**. For more information, refer to [HTTP request headers](/api-docs/static/rest-request-components.html#HTTP). ### downloadPostOrderDocument #### GET /post_order/document/{document_id} **Description:** This method downloads the file associated with the specified document ID. Access depends on the document’s state: * SUBMITTED: Only the document owner can download it * PUBLISHED: The document is no longer restricted to the owner and can be downloaded by authorized parties involved in the specific post‑order flow based on the **documentUsageType** **Note:** This method is currently restricted and requires a special **OAuth scope** not available to all users. **Note:** After a document is uploaded (but not yet published), its status is **SUBMITTED**. Once its identifier is linked to a post‑order entity through an eBay GraphQL mutation, the status changes to **PUBLISHED**. A post-order entity is part of eBay's order management for activities after purchase (such as returns). **Important!** The document must be in the **SUBMITTED** or **PUBLISHED** state to be downloadable. All documents (published or submitted) expire and become inaccessible after their expiration date. **Parameters:** - **document_id** (string) *required* - This path parameter is the unique identifier of the document associated with the file to be downloaded. This ID was returned in the [Location response header](/develop/guides-v2/using-ebay-restful-apis#responseheaders) when calling the **[uploadPostOrderDocument](/develop/api/sell/media_api#sell-media_api-post_order-uploadpostorderdocument)** method to upload the document. ### removePostOrderDocument #### DELETE /post_order/document/{document_id} **Description:** This method deletes a previously uploaded document by its document ID. Only documents in **SUBMITTED** state can be removed; documents in the **PUBLISHED** state cannot be deleted. **Note:** This method is currently restricted and requires a special **OAuth scope** not available to all users. **Note:** After a document is uploaded (but not yet published), its status is **SUBMITTED**. When its identifier is associated with a post‑order entity through an eBay GraphQL mutation, the status changes to **PUBLISHED**. A post-order entity is part of eBay's order management for activities after purchase (such as returns). **Important!** All documents, whether submitted or published, expire and become inaccessible after their expiration date. **Parameters:** - **document_id** (string) *required* - This path parameter is the unique identifier of the document associated with the file to be deleted. This ID was returned in the [Location response header](/develop/guides-v2/using-ebay-restful-apis#responseheaders) when calling the **[uploadPostOrderDocument](/develop/api/sell/media_api#sell-media_api-post_order-uploadpostorderdocument)** method to upload the document. ## Error Codes The following error codes may be returned by this API: ### REQUEST Errors #### 190201 - API_MEDIA **Description:** The image file size is larger than the limit. Please refer to the documentation. #### 190202 - API_MEDIA **Description:** The supplied image dimensions exceed the limit. Please refer to the documentation. #### 190203 - API_MEDIA **Description:** The supplied image is in a format that is not supported. Please refer to the documentation for a list of supported formats. #### 190013 - API_MEDIA **Description:** Unauthorized access. #### 190204 - API_MEDIA **Description:** No valid image can be downloaded from the provided imageUrl. Please refer to the documentation. #### 190200 - API_MEDIA **Description:** The image resource was not found. #### 190002 - API_MEDIA **Description:** Missing or invalid size. Size (in bytes) is required. #### 190003 - API_MEDIA **Description:** Maximum size exceeded for supported uploads. Please refer to documentation. #### 190004 - API_MEDIA **Description:** Title length exceeded. Please refer to documentation. #### 190005 - API_MEDIA **Description:** Description length exceeded. Please refer to documentation. #### 190006 - API_MEDIA **Description:** Title is required. #### 190014 - API_MEDIA **Description:** A video classification is required. #### 190016 - API_MEDIA **Description:** Markups are not permitted in the video title. #### 190017 - API_MEDIA **Description:** Markups are not permitted in the video description. #### 190001 - API_MEDIA **Description:** The specified video\_Id does not exist. #### 190007 - API_MEDIA **Description:** The content length does not match the content size specified. #### 190010 - API_MEDIA **Description:** The video's Content-Range is invalid. The Content-Range should be of the following bytes ((?:\[0-9\]+-\[0-9\]+)|\\\\\\\\\*)/(\[0-9\]+|\\\\\\\\\*) pattern. #### 190012 - API_MEDIA **Description:** The content length of the video is invalid. #### 190015 - API_MEDIA **Description:** The uploaded content must match the video size. #### 190011 - API_MEDIA **Description:** The video is already uploaded. #### 190008 - API_MEDIA **Description:** The content length is required. #### 190009 - API_MEDIA **Description:** The Content-Range specified is incorrect. Use Content-Range: bytes {1}}-{2}/{3} and Content-Length:{4} headers. #### 190050 - API_MEDIA **Description:** Missing or invalid 'languages' value(s). #### 190051 - API_MEDIA **Description:** Missing or invalid 'documentType' value. #### 190055 - API_MEDIA **Description:** Missing or invalid 'documentUrl' value. #### 190056 - API_MEDIA **Description:** Missing or invalid domain in 'documentUrl'. #### 190057 - API_MEDIA **Description:** Missing or malformed 'documentUrl'. #### 190058 - API_MEDIA **Description:** Missing or invalid 'request'. #### 190059 - API_MEDIA **Description:** Invalid value for ‘documentUrl’ was supplied. Failed to download document from 'documentUrl'. #### 190060 - API_MEDIA **Description:** Invalid value for ‘documentUrl’ was supplied. Please provide an HTTPS 'documentUrl'. #### 190061 - API_MEDIA **Description:** Invalid value for ‘documentUrl’ was supplied. File type could not be detected from ‘documentUrl'. #### 190062 - API_MEDIA **Description:** Invalid value for ‘documentUrl’ was supplied. Not an allowed file type for download from ‘documentUrl'. #### 190063 - API_MEDIA **Description:** Invalid value for ‘documentUrl’ was supplied. File size exceeds the maximum limit from ‘documentUrl'. #### 190052 - API_MEDIA **Description:** No document found with id {document\_id}. #### 190303 - API_MEDIA **Description:** Invalid post-order entity type supplied in the request. #### 190304 - API_MEDIA **Description:** Invalid document usage type supplied in the request. #### 190305 - API_MEDIA **Description:** The post-order entity type is missing from the request. #### 190306 - API_MEDIA **Description:** The post-order entity identifier is missing from the request. #### 190307 - API_MEDIA **Description:** The document usage type is missing from the request. #### 190309 - API_MEDIA **Description:** The uploaded file format is not supported. Supported formats are: jpeg, png, bmp, gif, jpg, and pdf. #### 190310 - API_MEDIA **Description:** The uploaded PDF exceeds the maximum allowed number of pages. #### 190311 - API_MEDIA **Description:** The post-order entity state does not allow new documents for the specified usage type. #### 190312 - API_MEDIA **Description:** The maximum number of documents for the specified post-order entity has been reached. #### 190313 - API_MEDIA **Description:** The uploaded file could not be processed. Please upload a valid file. #### 190314 - API_MEDIA **Description:** The uploaded file exceeds the maximum allowed size of 5 MB. #### 190315 - API_MEDIA **Description:** The file is missing from the request. Please upload a valid file. #### 190300 - API_MEDIA **Description:** Invalid or unknown post-order entity identifier supplied in the request. #### 190308 - API_MEDIA **Description:** The document identifier is missing from the request. #### 190301 - API_MEDIA **Description:** Invalid document identifier supplied in the request. #### 190302 - API_MEDIA **Description:** The document is no longer available because it has expired. ### APPLICATION Errors #### 190000 - API_MEDIA **Description:** There was a problem with an eBay internal system or process. Contact eBay developer support for assistance. ## Rate Limits See [API Call Limits](https://developer.ebay.com/develop/get-started/api-call-limits) on the eBay Developer Program. ## Resources ### Documentation - [eBay Developer Program](https://developer.ebay.com/) - [API Documentation](https://developer.ebay.com/develop/api/) - [SDKs and Widgets](https://developer.ebay.com/develop/sdks-and-widgets) - [Developer Community Forum](https://community.ebay.com/t5/Developer-Groups/ct-p/developergroup) ### Tools - [API Explorer](https://developer.ebay.com/my/api_test_tool) - [GraphQL Explorer](https://developer.ebay.com/my/graphql_explorer) ### Support - [Developer Support](https://developer.ebay.com/support/) - [API Status](https://developer.ebay.com/support/api-status) - [Release Notes](https://developer.ebay.com/develop/api/release_notes/) --- *Generated on 2026-07-10T17:14:39.338Z*