Vulcan/ Docs/ Post Sales to X

Post Sales to X

The Sales Bot can post every sale of your collection to an X account, as well as to your Discord channel. Each post shows the item's image, what it sold for, and who bought it, so every sale reaches your followers on X, not only the people already in your server.

It's available on every plan, including Free. You'll need a Sales Bot set up for your collection first; see Sales Bot.

There are two ways to connect an account:

  • Your own X developer app. Works on every plan. Takes about ten minutes to set up, and X bills your developer account for the posts.
  • Connect with X. On Growth and above you can sign in with X instead, with no developer account needed.

Connect with your own X developer app

1. Create an X developer account

  1. Go to the X Developer Console and sign in with the X account you want the sales to post from. The access token you create later posts as whichever account is signed in.
  2. Accept the Developer Agreement.

2. Create an app

  1. Click New App.
  2. Give it a name (for example, "My Collection Sales") and a short description.

3. Allow the app to post

In the app's settings, set its permissions to Read and write. The default, Read only, can't post.

If X asks for an app type, choose Web App, Automated App or Bot. If it asks for a callback URL or website, https://www.vulcan.xyz works for both. Vulcan doesn't use them.

4. Copy your keys

In the app's Keys and tokens, copy these four values. X only shows each one once, so keep them somewhere safe until you've pasted them into Vulcan.

X calls it Vulcan calls it
API Key (Consumer Key) API Key
API Key Secret (Consumer Secret) API Key Secret
Access Token Access Token
Access Token Secret Access Token Secret

Generate the Access Token and Secret after you set the permissions to Read and write. A token generated before that stays read-only, and X refuses its posts. If you changed the permissions afterwards, regenerate the token.

5. Add credits

X charges for API access per request, so posting needs credits on your developer account. In the Developer Console, add a payment method and buy credits. X lists the current price of each request type there, and new accounts are often offered some free credits.

Vulcan keeps the cost down: every sale in one transaction (a sweep, for example) goes out as a single post, and posts carry the item's image instead of a link where they can.

6. Paste the keys into Vulcan

  1. Go to vulcan.xyz/select, pick your server, and open Sales Bot.
  2. Click Post to X.
  3. Under Your own X app, paste the four values and click Save keys.

Vulcan checks the keys with X before saving them, and shows which X account they post as. They are stored encrypted. From then on, every new sale also posts to X.

Connect with X (Growth and above)

On the Post to X page, click Connect with X under Connect directly, sign in to the X account the sales should post from, and approve. That's it.

If your own app's keys are also saved, Vulcan posts through your app.

Change what the post says

The Post template on the same page sets the text of each post. Use these placeholders, and Vulcan fills them in for every sale:

Placeholder Becomes
{name} The item, for example "Punk #1234", or "Punk #1234 and 4 more" for a sweep
{collection_name} The collection
{price} The price in the chain's currency, for example 1.2Ξ
{usd_price} The price in USD, without the $ sign
{buyer} The buyer's ENS name or short wallet address
{seller} The seller's ENS name or short wallet address
{link} A link to the sale. Left out when the post carries the image

The template must include {name}. X cuts posts off at 280 characters.

Turn it off

Click Turn off at the top of the Post to X page. Your keys stay saved, so Turn on picks up where you left off. To delete the keys, click Remove keys.

Troubleshooting

When X refuses a post, the reason shows at the top of the Post to X page.

  • "X didn't accept these keys": the four values don't belong together. Check that they all come from the same app, and that you copied the whole of each one.
  • "X rejected the keys, so posting was switched off": the token was revoked or regenerated. Generate a new Access Token and Secret, save them again, and posting turns back on.
  • "X refused the post" with a 403: usually the token is read-only. Set the app to Read and write, regenerate the Access Token and Secret, and save them again. X also limits how many posts an account can make each day; if you hit that, Vulcan pauses for an hour and then carries on.
  • No API credits (402): add credits in the Developer Console. Vulcan tries again within the hour.
  • Nothing posts and there's no error: check that posting is turned on, and that the sale appears on the Sales Bot page. Vulcan posts to X the sales of the collections your Sales Bot tracks.