Etsy connector

Your Silux Chat bot verifies customers by their name and the email on their own orders in Etsy, then answers questions about their orders and order status from your live data.

Start free Set-up guide Etsy API docs

What your bot can do with Etsy

Orders and order status

Reads a verified customer’s recent orders from Etsy — order number, date, status and total, plus tracking where Etsy records it.

Customers ask: “Where is my order?” · “Has my last order been sent?”

Order numberOrder dateStatusTotalEmail addressTracking numberCourier

Set it up

Most businesses finish in under ten minutes. You need to be able to sign in to Etsy as an administrator.

Step 1 — in Etsy

Connect with Etsy (OAuth) — Silux Chat asks for read access to your shop's receipts.

Permissions (scopes) requested — read-only:

transactions_r

Least access: grant only the read permissions named above. Never use an owner or full-admin key where Etsy lets you create a restricted one.

Step 2 — in Silux Chat

1Open Dashboard → Integrations → Connectors and search for “Etsy”.
2
Fill in:
Field Example Stored
Shop ID 12345678 Setting
3Press Sign in with Etsy. The platform makes a real, read-only call to Etsy with a made-up customer and shows a tick or a cross for each capability, with Etsy’s exact error if something is refused.
4If this is your first way of verifying customers it is switched on automatically; otherwise press Use to verify customers. The platform then runs its chained test (verify → code → account → orders → invoices) with the built-in test customer — no real person is contacted.

Field	Example	Stored
Shop ID	12345678	Setting

There is no key to copy. You press “Sign in with Etsy”, approve read-only access on Etsy’s own page, and are returned to your dashboard. The access token is stored encrypted and refreshed automatically before it expires.

How customer verification works

STEP 1
Customer asks
They ask about their own account. The bot asks for their full name and the email address they used with you.
STEP 2
Matched in Etsy
Etsy has no customer search, so the customer’s own orders are looked up by that email. A record must name the exact email and a matching name: the surname exactly, and the first name or its first letter.
STEP 3
Code emailed
A 6-digit code goes to that email address — the one on the record. It is never sent to a mobile number typed in the chat.
STEP 4
Verified
The customer types the code. It is valid for 10 minutes and five wrong attempts cancel it. The verified session lasts 30 minutes, and only orders naming that email are shown.

If the details don’t match, the customer is told only that they couldn’t be matched — never which detail was wrong. If Etsy can’t be reached, the bot says it can’t check accounts right now rather than “no account found”. The bot is blocked in code from reading orders, invoices or bookings until verification succeeds. Full details: Customer identity verification & OTP.

What the bot can and cannot see

Can see (after verification)

Order number
Order date
Status
Total
Email address
Tracking number
Courier

Only these standard fields are mapped from Etsy’s responses. Everything else in the response is discarded before the bot sees it.

Never sees

passwords, security answers or login details
records belonging to anyone other than the verified customer
anything outside the fields listed alongside

Security

Sign-in tokens encrypted at rest
Credentials are stored encrypted, shown only masked after saving, and destroyed — not just hidden — when you disconnect.
Read-only look-ups
Every capability is a look-up. The connector cannot create, change or delete anything in Etsy.
HTTPS only
Calls go to the vendor’s HTTPS address, redirects are not followed, and private network addresses are refused.
Injection-safe
Values a customer types are cleaned before they are placed in Etsy’s search, and URL-encoded in addresses.
Other customers filtered out
A row that names a different customer’s email is dropped, whatever the vendor’s search returned.
Checked daily
Connections are re-tested every day, and the owner is emailed if a working connection starts failing.

More: Security & data protection.

Technical details

For developers and IT teams: the Etsy endpoints this connector reads, relative to https://openapi.etsy.com/v3/application. Values in braces come from the settings you enter.

Capability	Request	Standard fields returned
Orders and order status	GET`/shops/{shop_id}/receipts`	order_number, placed, status, total, email, tracking, courier

Test level: Documented-API tested. Each capability is run automatically against Etsy’s documented example responses and must produce the standard fields; your own connection is then tested with a real call when you connect. The bot receives these through the standard Account Connect endpoints, exactly as if you had built them yourself.

Troubleshooting

What you see	Likely cause and fix
“the vendor refused the credentials (401)” or (403)	The sign-in was revoked or has expired, or it lacks a read permission this connector needs. Sign in with Etsy again.
“That Shop ID doesn’t look right”	Enter it in the form shown, e.g. 12345678 — without https:// or a trailing slash.
“Silux Chat’s Etsy app is not registered yet”	Our sign-in app with Etsy isn’t available yet; our team is notified automatically. Email support@siluxcall.co.uk for timing or alternatives.
Customers are “not matched” although they exist	Customers are matched on their own orders by the email they give. Check a recent record names that email and the customer’s name (surname exactly).
A capability shows a cross but others work	That permission wasn’t granted in Etsy, or your Etsy plan doesn’t include that part of the API. Grant it and press Test.
“the vendor kept rate-limiting the request”	Etsy returned “too many requests” three times in a row. The platform already waits and retries automatically (up to 10 seconds, as Etsy asks); if it persists, ask Etsy about your API quota.
Results are empty for a verified customer	The records exist under a different email or customer record in Etsy, or none are recent. Check the customer’s record in Etsy directly.

Full error reference: Troubleshooting & error reference.

Frequently asked questions

Is the Etsy connection read-only?

Yes. Every request Silux Chat makes to Etsy is a look-up; none creates, changes or deletes anything in Etsy. Give the key or sign-in read-only permissions wherever Etsy offers them.

Do I need a developer to connect Etsy?

No. You sign in with Etsy in Dashboard → Integrations → Connectors and press “Sign in with Etsy”. The platform makes a real call to Etsy straight away and shows exactly which features work.

How does the bot know it is really my customer?

Etsy has no customer search, so the bot looks up the customer’s own orders by the email they give. A record must name that exact email and a matching name (surname, plus first name or initial) — then a one-time code is emailed to that address, never to a number typed in the chat. The code lasts 10 minutes, five wrong attempts cancel it, and a verified session lasts 30 minutes.

What happens if my Etsy key is revoked or expires?

The bot tells customers it can’t check their account right now — it never pretends there are “no orders”. Connections are re-tested daily and the account owner is emailed when a working connection starts failing. Reconnect it in Dashboard → Integrations → Connectors.

How has the Etsy connector been tested?

It is Documented-API tested: every capability is run automatically against Etsy’s documented example responses and must produce the standard fields. When you connect, it is tested again with a real call to your own Etsy account before your bot uses it.