Skip to content
Business productivity ⇄ Human resources

Amazon Seller Central to Lever integration — real-time data sync

Keep Amazon Seller Central and Lever in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Amazon Seller Central and Lever

Keep the people, teams, and status that Amazon Seller Central and Lever share aligned in real time, so a hire, role change, or departure recorded in one reaches the other within seconds.

Amazon Seller Central is a read-only source: Stacksync reads its data in real time and delivers it into Lever, so Lever always reflects the current state of Amazon Seller Central — without exports, scripts, or schedulers.

Each tool in Amazon Seller Central keeps its own list of who can use it: users, members, or agents, along with the team they sit on and whether they are still active. Lever is the authoritative record of the same people as employees, with their department, manager, and employment status. When those two are connected only by manual account admin or a periodic export, the work tools drift: new hires wait days for access, team and manager changes never catch up, and people who have left keep standing accounts.

Because the sync is field-level, each system keeps its own extras; only the shared facts, who a person is, which team they belong to, and whether their access should be on, are held in agreement.

Common use cases

  • 01 Land Amazon orders, reports, and settlement data in your warehouse or ERP as they are produced.
  • 02 Track price and inventory report changes across marketplaces from one queryable table.
  • 03 Consolidate Feedback, Interviews, and Notes into a warehouse for interviewer scorecard and time-to-fill reporting.
  • 04 Write enriched Sources, Tags, and Contact data back onto Opportunities from an outbound sourcing pipeline.

Common sync patterns

One employee directory

A person's name, title, contact details, or status corrected in either system updates the other, so both sides stop maintaining separate copies of the same person.

Org and team structure kept current

Department, team, and reporting-line changes from Lever keep the groups, queues, or projects in Amazon Seller Central assigned to the right people.

Where Amazon Seller Central routes or assigns work by person: assignments follow the org

When someone changes teams or managers in Lever, the queues, ownership, or approvals in Amazon Seller Central update to match, so work reaches whoever holds the role now.

What you can sync between Amazon Seller Central and Lever

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Amazon Seller Central objects Lever objects How this pairing syncs
Order Items Line-level SKU, quantity, and price data joined to orders in downstream systems. Users Lever team members (recruiters, hiring managers) with configurable roles; can be created via POST /users, deactivated, and reactivated through the API. Order Items is specific to Amazon Seller Central and Users to Lever — each maps to any object or custom field on the other side.
Listings / Catalog Items Product listing content and status, readable and updatable through the Listings and Feeds APIs. Stages Pipeline stage definitions that Opportunities move through; read to model funnel state and stage transitions in a database. Listings / Catalog Items is specific to Amazon Seller Central and Stages to Lever — each maps to any object or custom field on the other side.
FBA Inventory Fulfillable quantity by SKU, synced out for stock planning and replenishment. Feedback Interview feedback and scorecard forms attached to Opportunities; created via POST /opportunities/:id/feedback and consolidated into a warehouse for interviewer analytics. FBA Inventory is specific to Amazon Seller Central and Feedback to Lever — each maps to any object or custom field on the other side.
Shipments Inbound and outbound shipment records used to track fulfillment state. Interviews Scheduled interview panel events with times and interviewers; read for scheduling reporting and time-to-hire metrics, and creatable via the panels endpoint. Shipments is specific to Amazon Seller Central and Interviews to Lever — each maps to any object or custom field on the other side.
Financial Events Settlement, fee, and refund events synced to finance systems for reconciliation. Notes and Contacts Free-text Notes on Opportunities plus the underlying Contact (person) that dedupes multiple Opportunities; notes are posted via POST /opportunities/:id/notes and contact-level tags, sources, and links can be added back for attribution. Financial Events is specific to Amazon Seller Central and Notes and Contacts to Lever — each maps to any object or custom field on the other side.
Returns Return and refund records routed to support and finance workflows. Opportunities The core pipeline record for a candidate applying to a role; replaced the deprecated Candidates endpoint. Created via POST /opportunities and updated (stage, archive, links, tags, sources, files) through the API, and synced two-way with a database or HRIS. Returns is specific to Amazon Seller Central and Opportunities to Lever — each maps to any object or custom field on the other side.

How changes propagate between Amazon Seller Central and Lever

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Amazon Seller Central Lever Interval-based propagation

DetectionStacksync polls Amazon Seller Central for changes on an incremental schedule, reading only records changed since the previous pass. Historical and incremental syncs (mechanism not further specified).

DeliveryEach detected change is written to Lever through its API, with automatic retries and rate-limit backoff.

Lever Amazon Seller Central Sub-second propagation

DetectionLever notifies Stacksync of record changes through webhook events. Webhooks for candidate and application lifecycle events (applicationCreated, candidateStageChange, candidateArchiveStateChange, candidateHired,.

DeliveryAmazon Seller Central does not accept inbound record writes, so this direction carries requests rather than records: Amazon Seller Central's output flows back as field updates on the originating Lever records.

Rate-limit considerations

  • Amazon Seller Central: Per-operation token-bucket rate limits; bulk reads and writes should go through the asynchronous Reports and Feeds APIs instead of item-by-item calls.
  • Lever: 10 requests/second per API key with a token-bucket burst to ~20/s; POSTs that create candidates/applications are throttled to roughly 2/second. Sustained overage returns 429 with Retry-After. List endpoints are cursor-paginated at up to 100 records per page.
What ships with Amazon Seller Central ⇄ Lever

Connect Amazon Seller Central and Lever for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Amazon Seller Central–Lever connection.

Real-time

Real-time sync

Changes in Amazon Seller Central or Lever instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Amazon Seller Central or Lever data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Amazon Seller Central or Lever record.

Observability

Monitoring

Track your Amazon Seller Central ⇄ Lever sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Amazon Seller Central and Lever.

How the Amazon Seller Central and Lever connectors work

Amazon Seller Central

Integration surface
REST API (Selling Partner API, SP-API)
Authentication
SP-API app credentials (LWA client ID/secret, application ID, Merchant ID/Seller ID token, refresh token, region) entered into the Stacksync connection form
Change detection
Historical and incremental syncs (mechanism not further specified)
Capabilities
read
Rate limits
Per-operation token-bucket rate limits; bulk reads and writes should go through the asynchronous Reports and Feeds APIs instead of item-by-item calls
Amazon Seller Central setup guide

Lever

Integration surface
REST Data API (api.lever.co/v1)
Authentication
API key over HTTP Basic auth (key as username, blank password) for internal integrations, or OAuth 2.0 with 1-hour access tokens for partner integrations (auth.lever.co)
Change detection
Webhooks for candidate and application lifecycle events (applicationCreated, candidateStageChange, candidateArchiveStateChange, candidateHired, interview created/updated/deleted), plus incremental polling via created_at and updated_at range filters on Opportunities
Capabilities
read · write · webhooks
Rate limits
10 requests/second per API key with a token-bucket burst to ~20/s; POSTs that create candidates/applications are throttled to roughly 2/second. Sustained overage returns 429 with Retry-After. List endpoints are cursor-paginated at up to 100 records per page.
Lever setup guide
How it works

How to connect Amazon Seller Central to Lever — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Amazon Seller Central and Lever with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Amazon Seller Central connected
    Lever connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Amazon Seller Central and Lever objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Amazon Seller Central ⇄ Lever
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Amazon Seller Central Lever
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Amazon Seller Central and Lever integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

Related integrations

Every pair below is a real-time, two-way sync. Search all 468 integrations available for Amazon Seller Central and Lever.

Popular · 7 of 468
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.