SendMeby Boldswitch
Ok Send Me

Verified people, behind your product.

Open a SendMe request from your own product and get the status and the proof back, without ever handling NIN data, identity images, escrow state or an agent’s home address.

Keys are issued per partner through support in the app. Test mode is available from day one.

Three kinds of partner.

Listing platforms and agencies

A viewing button on every listing.

Open a hosted SendMe session from your listing page. Your renter picks an agent and pays; you get the request status back.

  • Hosted errand sessions, so the flow runs on SendMe and lands back on your page.
  • Webhooks for every status change, from accepted to report sent.
  • No NIN data, identity images or escrow state to handle on your side.
Merchants and logistics

Parcel runs from your order flow.

Create parcel requests with item type, size, value, pickup, drop and receiver, and track them to delivery.

  • Test mode with sm_test_ keys creates drafts that never match a real agent.
  • Agents near the pickup and heading toward the drop are ranked first.
  • Proof photos at pickup and delivery come back on the record.
Estates and property managers

Verified people for recurring work.

Cleaning, repairs and viewings across many units, with SendMe's verification and escrow on every job.

  • Hosted verification so your staff or tenants verify once, on SendMe.
  • One offer per job, held at acceptance, released on approval.
  • Signed webhooks retried up to 8 times, so your system never misses a step.

The integration, in five moves.

It mirrors the app exactly. A request is created, funded, matched to a verified agent, proven step by step, and closed by approval.

01
Get keys, start in test mode

Scoped sm_test_ and sm_live_ keys. Test-mode requests are real drafts that never match a real agent, so you can build the whole flow safely.

Scoped keys
02
Verify your users on SendMe

Hosted verification hands your user to SSYNC ID and back. You never touch the NIN or the identity images.

Hosted verification
03
Open a hosted errand session

Category, address, details and offer come from your system. Your user picks the agent, locks the price and funds it on SendMe, then lands back on your page.

Hosted session
04
Listen for status changes

Signed webhooks for every move: accepted, agreed, each of the four steps, awaiting approval, released, cancelled, disputed. Retried up to 8 times.

Signed webhooks
05
Read the record

Fetch the request: the locked price, the steps with timestamps, the proof media on signed URLs, and who approved. Show it to your customers.

OpenAPI 3.1 at /docs

The record is the product.

Every closed request returns the same shape: who did it, how far they were verified, what the price was, the four steps, the proof, and who approved. Embed it, store it, show it.

Escrow state lives on SendMe. Your system never holds money or moves it; it reads what happened.

Partner APIEarly access
KeysScoped sm_live_ and sm_test_ keys
Test modeDrafts that never match
Hosted flowsVerification and errand sessions
WebhooksSigned, retried up to 8 times
ReferenceOpenAPI 3.1 at /docs

What partners control, and what they don’t.

The record is only worth something because no partner can bend it. That is the whole value.

Yours to choose

You set the request up.

  • Category, address, details, schedule and the opening offer
  • Checklist items, parcel details or the service brief
  • Which webhooks you subscribe to
  • Where and how you display the record
Never in your hands

The record stays on SendMe.

  • Who is verified, and how
  • NIN data, identity images and agent home addresses
  • Escrow: holding, releasing, refunding
  • Editing or replacing any proof

Build on proof, not promises.

Get the app, run a request end to end, then ask support for test keys and the reference.