GoGetSSL MCP Tools & API Patterns
Overview
GoGetSSL is an SSL certificate reseller. An MSP holds one reseller account,
tops up a prepaid balance, and buys certificates for client domains from it.
The GoGetSSL MCP server (gogetssl-mcp) wraps the GoGetSSL API v1 at the
fixed host https://my.gogetssl.com/api and exposes 20 read tools. It never
orders, renews, reissues, cancels or pays for anything.
Connection & Authentication
Conduit asks for two fields in its web UI (/connect/gogetssl), stores them,
and forwards them to the MCP server as headers. Nothing is set on the client,
and Conduit drops any X-GoGetSSL-* header a client sends:
| Conduit field |
Header |
| Client-area username |
X-GoGetSSL-Username |
| API password |
X-GoGetSSL-Api-Password |
There is no Authorization header and no Bearer token. GoGetSSL's API uses a
two-step login: the server posts the username and API password to the
vendor's auth endpoint, gets back a session key, and sends that key as the
auth_key query parameter on every later call. The sidecar does this for
you, caches the key in memory for 12 hours, and if GoGetSSL rejects a cached
key it logs in again and retries once. You never handle the key.
Connect-time gotchas, all from Conduit's connect note:
- API password, not account password. The API password lives in Client
area > Reseller Modules > API settings. Conduit validates the pair by
logging in, and the account password fails with "GoGetSSL rejected the
username or API password".
- The credential can spend money. The same API password can place orders
and spend the balance through GoGetSSL's own API. Conduit only reads, but
if the password is exposed, regenerate it in Reseller Modules > API
settings.
- IP allowlist. If the GoGetSSL account restricts API access by IP,
Conduit's egress IP must be on the list, or every call fails at login.
Use gogetssl_account_get as the connection test. It returns the company,
contact email, reseller plan and currency, which also confirms which account
the credentials belong to.
Tool Surface
All 20 tools are listed flat in tools/list, all are read tier, and none
is admin-gated in Conduit (no tool is marked isAdmin). Conduit does not
cache GoGetSSL results yet, so every call goes to the vendor.
| Domain |
Tools |
| Account |
gogetssl_account_get, gogetssl_account_get_balance, gogetssl_account_get_total_orders |
| Orders |
gogetssl_orders_list, gogetssl_orders_list_ssl, gogetssl_orders_get_status, gogetssl_orders_get_statuses, gogetssl_orders_list_unpaid, gogetssl_orders_get_invoice |
| Invoices |
gogetssl_invoices_list, gogetssl_invoices_list_unpaid, gogetssl_invoices_list_by_period, gogetssl_invoices_get |
| Products |
gogetssl_products_list, gogetssl_products_list_ssl, gogetssl_products_list_prices, gogetssl_products_get |
| LEI |
gogetssl_lei_get_status |
| Validation |
gogetssl_dcv_get_domain_emails |
| CSR |
gogetssl_csr_decode |
gogetssl_orders_get_statuses and gogetssl_dcv_get_domain_emails are POST
requests at the vendor, but both are lookups that change nothing.
gogetssl_csr_decode is also a POST and is the one tool that sends no auth
key: it only decodes the CSR you pass it.
One Account, No Client Scoping
GoGetSSL has no concept of a client or sub-account inside a reseller
account. Every order sits in one flat list. To report per client:
- Pull orders with
gogetssl_orders_list.
- Group by
common_name (and the registrable domain under it, so
www.contoso.com and mail.contoso.com land together).
- Map domains to clients from your PSA or documentation platform. Say so in
the output when a domain could not be mapped instead of guessing.
Paging and Response Size
| Tool |
Paging |
gogetssl_orders_list |
Not paged by the vendor. Narrow it with status (active, processing, expired, revoked, rejected). |
gogetssl_orders_list_ssl |
limit 1-1000 (larger values are capped, vendor default 1000) and offset. The response echoes limit, offset and count. The server never pages for you: call again with offset + limit until a page comes back short. |
gogetssl_orders_get_statuses |
cids takes 1-100 numeric order IDs. Batch larger sets in groups of 100. |
gogetssl_invoices_list_by_period |
date_from / date_till in YYYY-MM-DD, at most 365 days apart. Without dates it returns the last 365 days. |
Two size limits apply. The server refuses a vendor response over 4 MB, with
an error telling you to narrow the query with a status filter, a limit, or a
shorter date range. Tool output is also truncated at about 60,000 characters,
so on a large account always pass status to gogetssl_orders_list rather
than pulling every order ever placed.
Errors
GoGetSSL reports errors as {error: true, message, description}, sometimes
with HTTP 200. The server checks the body as well as the status, so an error
envelope always surfaces as a tool error of the form
GoGetSSL API error (HTTP <status>) on <method> <path>: <hint>. <message>.
| Status / message |
Meaning |
Action |
| "GoGetSSL login failed" |
Username or API password rejected at login |
Check the pair in Conduit; confirm it is the API password; check the IP allowlist |
| 401 / 403, or a message about the auth key |
Session key rejected |
The server already re-logged in and retried once. If it still fails, the API password was likely regenerated: update it in Conduit |
| 404 |
Unknown order, invoice or product ID |
Re-list to confirm the ID |
| 429 |
Rate limited |
Wait for the Retry after Ns value in the message, then retry |
| "timed out or was cancelled" |
Request exceeded 30 seconds |
Narrow the query and retry |
| "redirect ... refusing to follow it" |
GoGetSSL answered with a redirect |
Treat as a vendor-side issue; retry later |
Argument errors come back before any vendor call: order IDs must be numeric,
dates must be YYYY-MM-DD, domains must be a bare FQDN (no scheme, path or
wildcard), and a CSR containing a private key is refused.
Rate Limits
GoGetSSL publishes no rate limit. Keep sweeps serial rather than firing many
calls at once, prefer one gogetssl_orders_get_statuses call over 100
separate gogetssl_orders_get_status calls, and back off on a 429.
Related Skills
1---2name: gogetssl-api-patterns3description: >4 GoGetSSL MCP fundamentals: the username plus API-password credential pair5 Conduit sends as X-GoGetSSL-* headers, the sidecar's cached auth-key login,6 the flat 20-tool read-only surface (none admin-gated), the single reseller7 account model with no client scoping, which list tools page and which do8 not, response-size limits, and GoGetSSL's error envelope.9when_to_use: >-10 When connecting GoGetSSL through Conduit, debugging a failed GoGetSSL tool11 call, or deciding which GoGetSSL list tool to page through. Use when:12 gogetssl api, gogetssl authentication, gogetssl api password, gogetssl13 connection error, gogetssl pagination, gogetssl mcp, or gogetssl tools.14metadata:15 source: https://skillmd.com/skills/wyre-ai/gogetssl-api-patterns16---1718# GoGetSSL MCP Tools & API Patterns1920## Overview2122GoGetSSL is an SSL certificate reseller. An MSP holds one reseller account,23tops up a prepaid balance, and buys certificates for client domains from it.24The GoGetSSL MCP server (`gogetssl-mcp`) wraps the GoGetSSL API v1 at the25fixed host `https://my.gogetssl.com/api` and exposes 20 read tools. It never26orders, renews, reissues, cancels or pays for anything.2728## Connection & Authentication2930Conduit asks for two fields in its web UI (`/connect/gogetssl`), stores them,31and forwards them to the MCP server as headers. Nothing is set on the client,32and Conduit drops any `X-GoGetSSL-*` header a client sends:3334| Conduit field | Header |35|---------------|--------|36| Client-area username | `X-GoGetSSL-Username` |37| API password | `X-GoGetSSL-Api-Password` |3839There is no `Authorization` header and no Bearer token. GoGetSSL's API uses a40two-step login: the server posts the username and API password to the41vendor's auth endpoint, gets back a session key, and sends that key as the42`auth_key` query parameter on every later call. The sidecar does this for43you, caches the key in memory for 12 hours, and if GoGetSSL rejects a cached44key it logs in again and retries once. You never handle the key.4546Connect-time gotchas, all from Conduit's connect note:4748- **API password, not account password.** The API password lives in Client49 area > Reseller Modules > API settings. Conduit validates the pair by50 logging in, and the account password fails with "GoGetSSL rejected the51 username or API password".52- **The credential can spend money.** The same API password can place orders53 and spend the balance through GoGetSSL's own API. Conduit only reads, but54 if the password is exposed, regenerate it in Reseller Modules > API55 settings.56- **IP allowlist.** If the GoGetSSL account restricts API access by IP,57 Conduit's egress IP must be on the list, or every call fails at login.5859Use `gogetssl_account_get` as the connection test. It returns the company,60contact email, reseller plan and currency, which also confirms which account61the credentials belong to.6263## Tool Surface6465All 20 tools are listed flat in `tools/list`, all are read tier, and **none66is admin-gated in Conduit** (no tool is marked `isAdmin`). Conduit does not67cache GoGetSSL results yet, so every call goes to the vendor.6869| Domain | Tools |70|--------|-------|71| Account | `gogetssl_account_get`, `gogetssl_account_get_balance`, `gogetssl_account_get_total_orders` |72| Orders | `gogetssl_orders_list`, `gogetssl_orders_list_ssl`, `gogetssl_orders_get_status`, `gogetssl_orders_get_statuses`, `gogetssl_orders_list_unpaid`, `gogetssl_orders_get_invoice` |73| Invoices | `gogetssl_invoices_list`, `gogetssl_invoices_list_unpaid`, `gogetssl_invoices_list_by_period`, `gogetssl_invoices_get` |74| Products | `gogetssl_products_list`, `gogetssl_products_list_ssl`, `gogetssl_products_list_prices`, `gogetssl_products_get` |75| LEI | `gogetssl_lei_get_status` |76| Validation | `gogetssl_dcv_get_domain_emails` |77| CSR | `gogetssl_csr_decode` |7879`gogetssl_orders_get_statuses` and `gogetssl_dcv_get_domain_emails` are POST80requests at the vendor, but both are lookups that change nothing.81`gogetssl_csr_decode` is also a POST and is the one tool that sends no auth82key: it only decodes the CSR you pass it.8384## One Account, No Client Scoping8586GoGetSSL has no concept of a client or sub-account inside a reseller87account. Every order sits in one flat list. To report per client:88891. Pull orders with `gogetssl_orders_list`.902. Group by `common_name` (and the registrable domain under it, so91 `www.contoso.com` and `mail.contoso.com` land together).923. Map domains to clients from your PSA or documentation platform. Say so in93 the output when a domain could not be mapped instead of guessing.9495## Paging and Response Size9697| Tool | Paging |98|------|--------|99| `gogetssl_orders_list` | Not paged by the vendor. Narrow it with `status` (`active`, `processing`, `expired`, `revoked`, `rejected`). |100| `gogetssl_orders_list_ssl` | `limit` 1-1000 (larger values are capped, vendor default 1000) and `offset`. The response echoes `limit`, `offset` and `count`. The server never pages for you: call again with `offset + limit` until a page comes back short. |101| `gogetssl_orders_get_statuses` | `cids` takes 1-100 numeric order IDs. Batch larger sets in groups of 100. |102| `gogetssl_invoices_list_by_period` | `date_from` / `date_till` in `YYYY-MM-DD`, at most 365 days apart. Without dates it returns the last 365 days. |103104Two size limits apply. The server refuses a vendor response over 4 MB, with105an error telling you to narrow the query with a status filter, a limit, or a106shorter date range. Tool output is also truncated at about 60,000 characters,107so on a large account always pass `status` to `gogetssl_orders_list` rather108than pulling every order ever placed.109110## Errors111112GoGetSSL reports errors as `{error: true, message, description}`, sometimes113with HTTP 200. The server checks the body as well as the status, so an error114envelope always surfaces as a tool error of the form115`GoGetSSL API error (HTTP <status>) on <method> <path>: <hint>. <message>`.116117| Status / message | Meaning | Action |118|------------------|---------|--------|119| "GoGetSSL login failed" | Username or API password rejected at login | Check the pair in Conduit; confirm it is the API password; check the IP allowlist |120| 401 / 403, or a message about the auth key | Session key rejected | The server already re-logged in and retried once. If it still fails, the API password was likely regenerated: update it in Conduit |121| 404 | Unknown order, invoice or product ID | Re-list to confirm the ID |122| 429 | Rate limited | Wait for the `Retry after Ns` value in the message, then retry |123| "timed out or was cancelled" | Request exceeded 30 seconds | Narrow the query and retry |124| "redirect ... refusing to follow it" | GoGetSSL answered with a redirect | Treat as a vendor-side issue; retry later |125126Argument errors come back before any vendor call: order IDs must be numeric,127dates must be `YYYY-MM-DD`, domains must be a bare FQDN (no scheme, path or128wildcard), and a CSR containing a private key is refused.129130## Rate Limits131132GoGetSSL publishes no rate limit. Keep sweeps serial rather than firing many133calls at once, prefer one `gogetssl_orders_get_statuses` call over 100134separate `gogetssl_orders_get_status` calls, and back off on a 429.135136## Related Skills137138- [certificate-expiry](../certificate-expiry/SKILL.md): expiry sweeps and renewal tiers139- [renewal-prep](../renewal-prep/SKILL.md): pricing, DCV approver emails and CSR checks140- [billing-reconciliation](../billing-reconciliation/SKILL.md): balance, unpaid items and per-client rebilling