Automate Jumpseller

What Jumpseller is

# Endpoint Structure All URLs are in the format: ```text https://api.jumpseller.com/v1/path.json?login=XXXXXX&authtoken=storetoken ``` The path is prefixed by the API version and the URL takes as parameters the login (your store specific API login) and your authentication token. *** # Version The current version of the API is **v1**. If we change the API in backward-incompatible ways, w

API host: api.jumpseller.com

Things people automate with Jumpseller

• Post new Jumpseller orders to SlackJumpseller → Slack
• Post new Jumpseller orders to TelegramJumpseller → Telegram
• Post new Jumpseller orders to Google ChatJumpseller → Google Chat
• Email customers from Gmail when a Jumpseller order landsJumpseller → Gmail
• Email customers from Resend when a Jumpseller order landsJumpseller → Resend
• Email customers from Postmark when a Jumpseller order landsJumpseller → Postmark
• Email customers from Mandrill when a Jumpseller order landsJumpseller → Mandrill

What HumDay can do in Jumpseller

62 documented operations change something in Jumpseller. The 50 most useful are listed here.

• POSTCreate a new Order./orders.json
• POSTCreate a new Customer./customers.json
• POSTCreate a new Page./pages.json
• POSTCreate a new Order History Entry./orders/{id}/history.json
• POSTCreate a new CustomerCategory./customer_categories.json
• PUTUpdate a new Customer./customers/{id}.json
• POSTAdds Customer Additional Fields to a Customer./customers/{id}/fields
• POSTCreate a new Hook./hooks.json
• POSTCreate a new Tax./taxes.json
• POSTCreate a new Product./products.json
• POSTCreate a new Category./categories.json
• POSTCreate a new Promotion./promotions.json
• POSTCreate a new Custom Field./custom_fields.json
• POSTCreate a new CheckoutCustomField./checkout_custom_fields.json
• POSTAdds Customers to a CustomerCategory./customer_categories/{id}/customers.json
• PUTModify an existing Order./orders/{id}.json
• DELETEDelete an existing Customer./customers/{id}.json
• POSTCreate a Store JSApp./jsapps.json
• POSTCreate a new Product Image./products/{id}/images.json
• POSTCreate a new Product Option./products/{id}/options.json
• POSTCreates a Shipping Method./shipping_methods.json
• POSTCreate a new Product Variant./products/{id}/variants.json
• POSTCreate a new Product Attachment./products/{id}/attachments.json
• POSTCreate a new Product DigitalProduct./products/{id}/digital_products.json
• POSTCreate a new Custom Field Select Option./custom_fields/{id}/select_options.json
• DELETEDelete Customers from an existing CustomerCategory./customer_categories/{id}/customers.json
• POSTCreate a Partnered Store/store/create.json
• DELETEDelete a Customer Additional Field./customers/{id}/fields/{field_id}
• PUTUpdate a Customer Additional Field./customers/{id}/fields/{field_id}
• DELETEDelete an existing Page./pages/{id}.json
• PUTUpdate a Page./pages/{id}.json
• DELETEDelete an existing CustomerCategory./customer_categories/{id}.json
• PUTUpdate a CustomerCategory./customer_categories/{id}.json
• POSTAdd an existing Custom Field to a Product./products/{id}/fields.json
• POSTCreate a new Product Option Value./products/{id}/options/{option_id}/values.json
• DELETEDelete an existing Hook./hooks/{id}.json
• PUTUpdate a Hook./hooks/{id}.json
• DELETEDelete an existing JSApp./jsapps/{code}.json
• DELETEDelete an existing Product./products/{id}.json
• PUTModify an existing Product./products/{id}.json
• DELETEDelete an existing Category./categories/{id}.json
• PUTModify an existing Category./categories/{id}.json
• DELETEDelete an existing Promotion./promotions/{id}.json
• PUTUpdate a Promotion./promotions/{id}.json
• DELETEDelete an existing CustomField./custom_fields/{id}.json
• PUTUpdate a CustomField./custom_fields/{id}.json
• DELETEDelete an existing Shipping Method./shipping_methods/{id}.json
• PUTUpdate a Shipping Method./shipping_methods/{id}.json
• DELETEDelete an existing CheckoutCustomField./checkout_custom_fields/{id}.json
• PUTUpdate a CheckoutCustomField./checkout_custom_fields/{id}.json

What HumDay can read from Jumpseller

These are the operations a schedule or a trigger can watch.

• GETRetrieve a Product List from a query./products/search.json
• GETRetrieve a single Customer by email./customers/email/{email}.json
• GETRetrieve a single Order./orders/{id}.json
• GETRetrieve a single Customer by id./customers/{id}.json
• GETRetrieves the Customer Additional Field of a Customer./customers/{id}/fields
• GETRetrieve all Orders./orders.json
• GETRetrieve all Customers./customers.json
• GETRetrieve orders filtered by Order Id./orders/after/{id}.json
• GETRetrieve all Order History./orders/{id}/history.json
• GETRetrieve all Store's Payment Methods./payment_methods.json
• GETRetrieve all Customer Categories./customer_categories.json
• GETRetrieves the customers in a CustomerCategory./customer_categories/{id}/customers.json
• GETCount all Orders./orders/count.json
• GETCount all Customers./customers/count.json
• GETRetrieve a single Customer Additional Field./customers/{id}/fields/{field_id}
• GETRetrieve a single Page by id./pages/{id}.json
• GETRetrieve a single Payment Method./payment_methods/{id}.json
• GETRetrieve a single CustomerCategory./customer_categories/{id}.json
• GETRetrieve all Hooks./hooks.json
• GETRetrieve all Pages./pages.json
• GETRetrieve all Taxes./taxes.json
• GETRetrieve all the Store's JSApps./jsapps.json
• GETRetrieve all Products./products.json
• GETRetrieve all Countries./countries.json
• GETRetrieve all Categories./categories.json
• GETRetrieve all Promotions./promotions.json
• GETRetrieve all Fulfillments./fulfillments.json
• GETRetrieve all Store's Custom Fields./custom_fields.json
• GETRetrieve all Store's Shipping Methods./shipping_methods.json
• GETRetrieve orders filtered by status./orders/status/{status}.json
• GETRetrieve the Fulfillments associated with the Order./order/{id}/fulfillments.json
• GETRetrieve all Checkout Custom Fields./checkout_custom_fields.json
• GETRetrieve Store Information./store/info.json
• GETCount all Pages./pages/count.json
• GETCount all Products./products/count.json
• GETRetrieve statistics./partners/stores.json
• GETRetrieve Store Languages./store/languages.json
• GETCount all Categories./categories/count.json
• GETCount all Fulfillments./fulfillments/count.json
• GETRetrive store creation status./store/check_status.json
• GETRetrieve a single Hook./hooks/{id}.json
• GETRetrieve a single Tax information./taxes/{id}.json
• GETRetrieve a JSApp./jsapps/{code}.json
• GETRetrieve a single Product./products/{id}.json
• GETRetrieve a single Category./categories/{id}.json
• GETRetrieve a single Promotion./promotions/{id}.json
• GETRetrieve a single Fulfillment./fulfillments/{id}.json
• GETRetrieve a single CustomField./custom_fields/{id}.json
• GETRetrieve a single Shipping Method./shipping_methods/{id}.json
• GETRetrieve a single Country information./countries/{country_code}.json

How automating Jumpseller works

1. Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
2. Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
3. See it proven. The program runs and shows you the result before it is allowed near your live Jumpseller account.
4. Grant access, then go live. You approve the specific Jumpseller operations it may use — and only those.

Popular Jumpseller integrations

Connect Jumpseller to the tools people pair it with most.

• Jumpseller and OData for namespace microsoft.graphintegration
• Jumpseller and Cloudflareintegration
• Jumpseller and NetBoxintegration
• Jumpseller and GitHubintegration
• Jumpseller and Mistintegration
• Jumpseller and Loket.nlintegration
• Jumpseller and Atlassian The Jira Cloud platformintegration
• Jumpseller and Magento B2Bintegration
• Jumpseller and Stripeintegration
• Jumpseller and Zuora Reference Billingintegration
• Jumpseller and bunqintegration
• Jumpseller and DocuSignintegration

Automate Jumpseller with these

• Magento B2B455 operations
• Klaviyo345 operations
• Agco ATS AGCO277 operations
• BeezUP Merchant210 operations
• Rebilly184 operations
• reverb163 operations
• Swagger API2Cart141 operations
• Just Eat UK97 operations
• Billbee75 operations
• Velopayments Velo Payments75 operations
• Apigee Marketcheck71 operations
• eBay Marketing69 operations

Categories

• E-commerce

Questions about Jumpseller automation

Can HumDay connect to Jumpseller?

Yes. HumDay reads Jumpseller's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 142 operations are documented.

Do I need to write code to automate Jumpseller?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Jumpseller account.

What can HumDay do in Jumpseller?

62 of the 142 documented operations change something in Jumpseller, and 80 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Jumpseller account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Jumpseller is held behind that approval.

Where this came from

The operations above are read from a published API description for Jumpseller at api.jumpseller.com/swagger.json. Descriptions are the provider’s own words, not ours. Last published 2021-08-23.