Identity API

Name: Identity API API
Brand: Identity API
Availability: InStock

✓ Official Vendor SpecIdentity AuthAuthenticationoauth21 EndpointsREST

For Agents

Authenticate an eBay user and retrieve their account profile fields via OAuth 2.0 'Sign in with eBay'.

Connect the Identity API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Identity API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Identity API API.

Retrieve the authenticated eBay user's account profile via GET /user/

Power 'Sign in with eBay' so apps avoid storing PII themselves

Confirm identity for an OAuth-authorised eBay user before granting account access

Pull only the profile fields permitted by the user's granted scopes

GET STARTED

Start building with Identity API API

Explore with Jentic

View OpenAPI Document

The eBay Identity API returns the authenticated user's account profile information so an application can offer 'Sign in with eBay' without storing personal data itself. The single GET /user/ endpoint, scoped through eBay's OAuth 2.0 flow, lets an integrator confirm who a user is and pull verified profile fields rather than asking the user to fill them in. Access to most profile fields is gated by OAuth scope and developer approval — eBay only releases sensitive PII to vetted business partners.

Use Cases

Patterns agents use Identity API API for, with concrete tasks.

★ Sign in with eBay

Marketplaces, dropshipping tools, and third-party seller dashboards offer 'Sign in with eBay' so users do not need yet another account. The application redirects the user through eBay's OAuth flow, then calls GET /user/ to read the verified profile and create a local session without storing the user's password.

Exchange the eBay OAuth authorisation code for an access token, call GET /user/, and create a local user record from the returned profile.

Seller Onboarding Pre-fill

Tools that help eBay sellers manage listings, repricing, or shipping use the Identity API to pre-fill onboarding forms with the seller's verified eBay handle and account fields. This reduces friction and avoids the user retyping data the host already trusts.

Call GET /user/ after OAuth and pre-populate the seller onboarding form with username and account email.

Account Linking and Audit

Integrations that sync eBay activity into an external CRM or accounting system call GET /user/ at link-time to record exactly which eBay account was authorised. Storing the eBay user identifier alongside the OAuth token makes downstream reconciliation against eBay activity unambiguous.

Call GET /user/ on token exchange and persist the eBay user identifier against the local CRM contact for future reconciliation.

AI Agent Identity Confirmation

An AI agent acting on a user's eBay account uses Jentic to call the Identity API and confirm whose account the OAuth token represents before performing sensitive operations like listing changes or payouts. Jentic isolates the OAuth credential and surfaces the single profile operation by intent.

Search Jentic for 'get the current eBay user', load the GET /user/ schema, and execute it to confirm which eBay account the active OAuth token represents.

Key Endpoints

1 endpoints — the ebay identity api returns the authenticated user's account profile information so an application can offer 'sign in with ebay' without storing personal data itself.

METHOD

PATH

DESCRIPTION

GET

/user/

Retrieve the authenticated eBay user's account profile.

GET

/user/

Retrieve the authenticated eBay user's account profile.

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

eBay OAuth access tokens are stored in the encrypted Jentic vault (MAXsystem) and injected at call time. The raw token never appears in agent prompts, tool outputs, or logs, which matters because a leaked eBay OAuth token can act on behalf of the user.

Intent-based discovery

The Identity API exposes a single operation. Agents search Jentic for 'get the current eBay user' and receive the GET /user/ schema directly, so they can confirm the active user without reading eBay's developer docs.

Time to first call

Direct eBay Identity integration: 1-2 days for OAuth flow, scope handling, and refresh-token logic. Through Jentic: under 1 hour once the OAuth credential is stored — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

eBay Finances API

Pair Identity authentication with seller payouts and transactions for a fuller seller view.

Use Identity to confirm the user, then call Finances to retrieve their payout history.

Complementary

eBay Sell Account API

Manage seller account preferences once the user's identity has been confirmed via Identity.

Use after Identity confirms the active seller, when the workflow needs to update fulfilment, payment, or return policies.

Alternative

PayPal Orders API

Alternative OAuth-based identity assertion when the user signs in with PayPal instead of eBay.

Choose PayPal when the integration is broader e-commerce checkout rather than eBay-specific seller tooling.

FAQs

Specific to using Identity API API through Jentic.

What authentication does the eBay Identity API use?

The eBay Identity API uses OAuth 2.0. Your application redirects the user through eBay's authorisation flow, exchanges the resulting code for an access token, and calls GET /user/ with that token. Through Jentic the OAuth credential is stored encrypted in the vault and injected at call time, so the agent never sees the raw token.

Can I get every eBay user's profile fields?

No. eBay restricts which profile fields are returned based on the OAuth scopes your application has been granted, and several account fields are only released to developers approved by eBay business units. Treat the GET /user/ response as a permitted subset, not a full PII record.

What are the rate limits for the eBay Identity API?

Rate limits are not declared in the OpenAPI spec but follow eBay's standard developer programme limits, which are applied per application and per call type and surface as 429 responses when exceeded. Identity is typically called once per session, so quota is rarely the bottleneck.

How do I confirm the active eBay user through Jentic?

Run pip install jentic, then search Jentic for 'get the current eBay user', load the schema for GET /user/, and execute it after exchanging your OAuth code. Jentic injects the bearer access token from your stored eBay credentials. Sign up at https://app.jentic.com/sign-up.

Can I use Identity to register a new eBay user?

No. The API only reads the authenticated user's profile; new account registration happens on eBay itself. Pair the Identity API with eBay's OAuth flow so users sign up on eBay and your app reads their profile only after they consent.

Does the API return seller-specific fields like store name?

Identity returns account-level profile fields. Seller-specific data such as store performance, payouts, or finances lives in the seller-side APIs (for example apiz.ebay.com/sell-finances) and requires the corresponding OAuth scopes.