Skip to main content
Læs siden på dansk You connect Webshipper with an API token, not with a login redirect. You create the token yourself in Webshipper and paste it in the portal together with your account name. Consile checks the token with Webshipper and stores it encrypted. Your AI never sees the token itself.
You must have connected your AI (Claude or ChatGPT) and have an active Webshipper subscription in the portal first, or have the system included in your plan (the free edition or the Consile Studio membership). The Webshipper account must be on Webshipper Pro or Advanced, which include API access. In Consile, anyone on the team can connect an agreement that is not connected yet. Only an administrator can reconnect it or disconnect it. The connection applies to the whole company.

Step 1: Find the account name and create an API token in Webshipper

1

Find your account name

Log in to Webshipper. The account name is what comes before .webshipper.io in the address bar, for example myshop in myshop.webshipper.io.
2

Create an API token

Go to Settings → Access and tokens, and click Create API token. Give the token a name you will recognise, for example Consile. That makes it easy to find if the access must be revoked later.
3

Copy the token

Copy the token right away, and keep it secret. It gives access to your Webshipper account.
A token belongs to exactly one Webshipper account. There is nothing to choose afterwards, because the account name and the token decide which data Consile can read. If you have several accounts, for example one per brand or country, you need one token per account (see Multiple agreements).

Step 2: Paste the account name and token in the portal

1

Open the form in the portal

Open the Webshipper connector in the portal. Click Connect now at the top of the page, or Connect next to the agreement on the Connections card. The portal calls each connection to a system an agreement. If you have not accepted Consile’s terms yet, the portal shows them first. A short form opens with a step-by-step guide at the top and two fields. There is no redirect to an external page.
2

Fill in the fields

If you paste the whole address from the browser, for example https://myshop.webshipper.io/orders, Consile uses only the account name (myshop). Copy the whole token, and make sure nothing else comes along.
3

Save

Click Connect. Consile first checks the token with Webshipper. If Webshipper refuses it, nothing is stored, and the form shows an error (see If the connection is refused). Otherwise the token is encrypted and stored under your account only.
The Webshipper is ready screen shows the connector’s address, https://mcp.consile.ai/webshipper/mcp. If you have not already added it in your AI, copy it and add it as a custom connector (see Connect Claude). Click Go to connector to return to the Webshipper page. Under Overview in the portal, Webshipper now shows as Connected, and the agreement takes the account’s name, for example myshop.webshipper.io.
The connection is shared by the whole company, so colleagues do not have to connect Webshipper again. An administrator gives them access under Team, and each colleague adds the address in their own AI and logs in with their own Consile login. See Team.

If the connection is refused

If Webshipper refuses the token or the account name, the form shows The system rejected the key. Check that it was copied correctly and is still active, then try again. Nothing is stored, and a connection that already worked is unchanged.
  • Wrong token: check that the whole token was copied, and that it has not been deleted in Webshipper.
  • Wrong account name: Webshipper does not know the account. Check the spelling in the address bar when you are logged in to Webshipper. Enter only the account name, not .api.webshipper.io or anything else.
  • No API access: the account must be on Webshipper Pro or Advanced.
If Webshipper does not answer during the check, the connection is stored anyway. An error then only shows up at the first lookup (see If a lookup fails).

Multiple agreements

Each agreement on the Connections card covers one Webshipper account and becomes its own named connector in your AI. If you have several Webshipper accounts, do this:
1

Add an agreement

Open the Webshipper connector in the portal. On the Connections card, an administrator clicks Add agreement (149.50 kr/mo.). The amount is excl. VAT and is added to the existing subscription.
2

Connect the new agreement

When the new agreement is ready (typically after a few seconds), click Connect next to it and paste the other Webshipper account’s account name and API token.
3

Add the address in your AI

Each agreement has its own address, for example https://mcp.consile.ai/webshipper-2/mcp. Copy it with the copy icon next to the agreement, and add it as an extra connector in your AI.
Under the Consile Studio membership there is no button to add an agreement. One more account costs full price under the membership. Write to support@consile.dk, and Consile sets it up. If an agreement should be removed again, see the section Revoke access below.

What exactly am I approving?

Read and write, with confirmation

The token gives access to your Webshipper account. Consile only changes something when a write tool is confirmed with confirm: true, and an administrator can set users to Read only. See Webshipper.

One account per token

Every call goes to the Webshipper account the account name points to. No lookup can reach another account.

Encrypted per customer

The token is stored encrypted with a key that applies only to your own account. It is never logged and is only sent to Webshipper.

Your AI never sees it

Your AI is never given the token itself. It only receives answers to your questions.
The token’s permissions. If the token lacks access to an area in Webshipper, for example shipments or shipping rates, it is still accepted when you connect. The tools that use that area then fail with an explanatory message. Create a new token in Webshipper with access to that area, and connect again with it.

Revoke access

  • In the portal: an administrator clicks the menu (the three dots) next to the agreement on the Connections card and confirms with Disconnect. The stored token for the agreement is then deleted at Consile right away. The subscription continues.
  • Remove an agreement: if you have several agreements, an administrator chooses Remove the agreement in the same menu and confirms with Remove agreement. This deletes the agreement’s token at Consile and removes the agreement from the subscription. If you remove an agreement other than the last one in the list, the last agreement’s connection moves up into the free slot and takes its address. So check the addresses in your AI afterwards. You remove the last agreement by cancelling the subscription under Subscription.
  • In Webshipper: the token does not expire on its own. Delete it under Settings → Access and tokens, and it stops working right away. Your AI is then told that Webshipper must be connected again.

If a lookup fails

  • “webshipper is not connected yet. Connect it here: …”: no token has been stored for this agreement yet, or it has been disconnected. Open the link (it works for 10 minutes), or connect in the portal as described in step 2. For an extra agreement, the message says, for example, webshipper-2.
  • “Webshipper rejected the connection’s credential. Reconnect Webshipper in the Consile portal, then try again.”: Webshipper refuses the token, typically because it was deleted in Webshipper. Create a new token, and an administrator reconnects with it. An administrator can also ask your AI on the agreement’s address for a new connection link. It opens the form for exactly that agreement, and the new token replaces the old one.
  • “Webshipper refused this request: the connected account does not have the permission or the licence it needs. …”: the token works, but lacks access to the area your AI asked about. See the note on the token’s permissions above.
  • “Webshipper is limiting how fast this connection may call it. …”: Webshipper allows about 2 calls per second per token. Wait a moment, and ask for less at a time.
  • “Webshipper could not find what was asked for. …”: the order, shipment or other id does not exist on the account. Ask your AI to find it with a search first, for example search_orders. Remember that the shop’s order number is not Webshipper’s id.
  • “Webshipper rejected the request: a value in it was not accepted.”: Webshipper has refused a value in the call, for example a shipping rate that does not belong to the order channel. On a write, the message also says Nothing was written.
  • “The arguments were not accepted: …”: your AI sent an argument the tool does not accept, for example a period longer than 92 days. The message names the argument, and your AI usually corrects the call itself.
  • “Webshipper did not answer or is having problems. …”: Webshipper did not answer in time or is having problems. Try again in a moment.
  • “The request was sent to Webshipper, but no usable answer came back, …”: the outcome of a write is unknown. Check the order or shipment in Webshipper before trying again, so you do not book or create twice.
  • “Tool invocation failed.”: the general error for everything else. Try again, and narrow the question.
  • If it keeps happening, contact support@consile.dk with the time and the question you asked.
More about data processing in Security & data.