Skip to main content
Neo connects to the Sherweb Service Provider API. With it connected, an agent can:
  • Read customers, their configured platforms, subscriptions, charges and usage
  • Look up a customer’s catalogue, the price per billing cycle and commitment term, and the platform details an order needs
  • Order a product a client does not hold yet, after a technician approves it
  • Cancel a subscription, after a technician approves it
  • Add or remove seats on an existing subscription with Change License Seats

​
Connect Sherweb

1

Collect your API credentials

In the Sherweb Cumulus portal, open Security → APIs and copy the Client ID, Client Secret and Subscription Key.
2

Save them in Neo

Open Integrations, select Sherweb, enter the three values, and click Save.
3

Map each company

On the Companies page, open a company, add a Sherweb row under Marketplace Company IDs and pick the customer from the dropdown. Agents use this customer for orders and cancellations, and each approval request names it.

​
What agents can do

Agents call Sherweb through the Vendor API tool, which is added when you give the agent Sherweb permissions in its settings. Each permission group has its own access level: The access profiles are Read Only, Helpdesk (every change asks a technician first) and IT Admin (no approval, except the two changes below). You can set approval per permission group.
A new order and a subscription cancellation always ask a technician for approval, in every profile. Sherweb bills you for an order, and Microsoft does not let you reduce or cancel an annual commitment after its first days.
A configured platform’s details can hold credentials. Before an agent or a script sees them, Neo replaces the value of each field whose name reads as a password, secret, token or key with [redacted by Neo]. The field stays in the answer.

​
Buying a product a client does not hold

  1. The agent finds the product in the client’s catalogue. In Sherweb each SKU is one product on one billing cycle and commitment term.
  2. It reads the price, and configures the platform the product needs when the client does not have it yet.
  3. It validates the order with Sherweb, which places nothing.
  4. It asks a technician to approve the order. The request names the product and SKU, the quantity, the billing cycle, the commitment term and the price.
  5. After approval, it places the order with exactly those values and follows it until Sherweb reports success.
  6. For a Microsoft product, once the licence shows in the client’s Microsoft 365 tenant, the agent assigns it if it has the M365 Licensing permission; otherwise it uses your licensing tool, such as CIPP, or hands the step to a technician.

​
Seat changes

To add or remove seats on a subscription the client already holds, the agent uses Change License Seats. The Vendor API tool refuses every subscription amendment. Change a billing term or commitment in Sherweb.