Skip to main content

Connect Greentree (credentials, Save & connect, Ping)

You need Sprintsuite to reach the company’s on-prem Greentree Web Services API so catalogues, links, CSV export gates, and invoice pushes can run.

When you need this

You need Sprintsuite to reach the company’s on-prem Greentree Web Services API so catalogues, links, CSV export gates, and invoice pushes can run.

Before you start

  • Greentree integration is on for the tenant.

  • You have Read & Write on Integrations for the billable company.

  • You have the Greentree Web Services URL, username, password, API Key (Greentree serial), and Company code (required for AP invoice pushes and other writes).

Steps

  1. Go to Settings → Integrations → Greentree → Credentials.

  2. Enter:

  • URL — Greentree Web Services endpoint (HTTPS).

  • Username / Password — integration account.

  • API Key (Greentree serial).

  • Company code — Greentree company used for writes (not the -1 Ping placeholder).

Greentree Credentials form before connect
  1. Click Save & connect.

  2. Sprintsuite saves the values and runs a live /Ping. On success you see a green Connected status (and typically “Connected to Greentree on …”). Secrets stay hidden while connected; blank password/API key fields mean “keep saved value”.

Greentree Credentials Connected status after successful Ping

[Video: Save & connect flow]

What success looks like

  • Status shows Connected.

  • Other Greentree tabs allow Sync / ReSync (subject to permissions).

  • Company code is set if you will push AP invoices.

If it fails

  • Ping fails → values may still save, but status stays disconnected with a reason. Check URL, API enabled on Greentree, credentials, and network allowlisting.

  • “Reached Greentree but /Ping returned HTTP …” → URL or API path wrong; confirm / -1 /Ping style reachability with your Greentree admin.

  • Writes fail later with missing company code → return here and set Company code, then Save & connect again.

Did this answer your question?