Skip to main content

GET/topic/{topic_id}

This method allows applications to retrieve details for the specified topic. This information includes supported schema versions, formats, and other metadata for the topic.

Applications can subscribe to any of the topics for a supported schema version and format, limited by the authorization scopes required to subscribe to the topic.

A topic specifies the type of information to be received and the data types associated with an event. An event occurs in the eBay system, such as when a user requests deletion or revokes access for an application. An event is an instance of an event type (topic).

Specify the topic to retrieve using the topic_id URI parameter.

Note: Use the getTopics method to find a topic if you do not know the topic ID.

Input

Resource URI

GET https://api.ebay.com/commerce/notification/v1/topic/{topic_id}

This method is supported in Sandbox environment. To access the endpoint, just replace the api.ebay.com root URI with api.sandbox.ebay.com

URI parameters

ParameterTypeDescription
topic_idstringThe unique identifier of the notification topic for which the details are retrieved. Use getTopics to retrieve the topic ID.

Occurrence: Required

HTTP request headers

All requests made to eBay REST operations require you to provide the Authorization HTTP header for authentication authorization.

All other standard RESTful request headers are optional. For more information on standard RESTful request headers, see the HTTP request headers- opens rest request components page table.

OAuth scope

This request requires an access token created with the client credentials grant flow, using one or more scopes from the following list (please check your Application Keys page for a list of OAuth scopes available to your application):

https://api.ebay.com/oauth/api_scope

See OAuth access tokens for more information.

Request payload

This call has no payload.

Request fields

This call has no field definitions.

Output

HTTP response headers

This call has no response headers.

Response payload

Response fields

Output container/fieldTypeDescription
authorizationScopesarray of string

The authorization scopes required to subscribe to this topic.

Occurrence: Conditional

contextContextEnum

The business context associated with this topic.

Occurrence: Always

descriptionstring

The description of the topic.

Occurrence: Always

filterableboolean

The indicator of whether this topic is filterable or not.

Occurrence: Always

scopeScopeEnum

The scope of this topic.

Occurrence: Always

statusStatusEnum

The status of this topic.

Occurrence: Always

supportedPayloadsarray of PayloadDetail

The supported payloads for this topic.

Occurrence: Conditional

supportedPayloads.deliveryProtocolProtocolEnum

The supported delivery protocols.

Occurrence: Always

supportedPayloads.deprecatedboolean

A deprecation indicator.

Occurrence: Always

supportedPayloads.formatarray of FormatTypeEnum

The supported format. Presently, JSON is the only supported format.

Occurrence: Always

supportedPayloads.schemaVersionstring

The supported schema version.

Occurrence: Conditional

topicIdstring

The unique identifier for the topic.

Occurrence: Always

HTTP status codes

This call can return one of the following HTTP status codes. For an overview of the status codes, see HTTP status codes in Using eBay RESTful APIs.

StatusMeaning
200OK
404Not Found
500Internal Server Error

Error codes

For more on errors, plus the codes of other common errors, see Handling errors.

CodeDomainCategoryMeaning
195000API_NOTIFICATIONAPPLICATIONThere was a problem with an eBay internal system or process. Contact eBay developer support for assistance.
195002API_NOTIFICATIONREQUESTInvalid or missing topic id.

Warnings

This call has no warnings.

Samples

This call has no samples.