We Ship You API integration services for LATAM shipping, recharge, and OpenData logistics

1) Authentication and session control module

We implement token management around the documented authentication flow (`/api/v1/authentication`) and align it with your backend session model. This makes We Ship You account-linking usable for portal products, customer support tools, and automated workflow engines.

Concrete use: map user identity and token expiry (`iat` / `exp`) to internal access-control policies, so your team can run secure scheduled pulls without storing raw credentials in business apps.

2) Shipment rates and booking integration module

We expose shipping rate queries and shipment creation endpoints (`/api/v1/shipments/rates`, `/api/v1/shipments`) through your own normalized schema. Your operations team can compare route cost, carrier options, and ETA logic from one endpoint.

Concrete use: finance teams can reconcile quoted versus executed shipping cost by lane, then push variances to BI tools or ERP ledgers.

3) Shipment lifecycle and status export module

Integration covers list/detail/update/cancel operations for shipments so order managers can trigger customer notifications or flag stalled packages. We include structured status events and pagination strategy for high-volume exports.

Concrete use: unified logistics data export into a daily warehouse feed for SLA monitoring and dispute evidence packages.

4) Mobile recharge provider and product intelligence module

We integrate provider, provider-description, and product-description endpoints under `/api/v1/mobile-recharges/*` so teams can power top-up catalog pages, destination filtering, and per-provider margin checks.

Concrete use: customer-success teams can detect failed product mappings early and reduce manual support tickets.

5) Recharge transaction operations module

We build read and create flows for recharge operations (`/api/v1/mobile-recharges/recharges`) with idempotency guidance and retry-safe error handling. This module is designed for controlled OpenData feeds into accounting and customer notification channels.

Concrete use: daily recharge transaction export with country, provider, and amount dimensions for compliance-ready audit trails.

6) Funding and sub-account governance module

For teams with multiple operators, we integrate add-funds and add-sub-account endpoints (`/api/v1/add-funds`, `/api/v1/add-sub-account`). This enables delegated operations while preserving a central ledger and role model.

Concrete use: branch-level operators execute tasks with constrained permissions, while headquarters receives consolidated funding and activity reports.

Scenario A: Cross-border fulfillment command center

Business context: a LATAM-focused e-commerce operator ships from the U.S. to multiple destinations and needs a single dashboard for quotes, shipment creation, and tracking.

Data/API involved: rates endpoint, shipment create/list/detail, and tracking events. OpenData mapping: logistics data is standardized into lane, carrier, and milestone objects consumed by BI and support tooling.

Scenario B: Recharge operations reconciliation

Business context: a digital services provider sells top-ups and must reconcile provider-level transactions against internal payment records each day.

Data/API involved: recharge provider catalogs plus recharge transaction endpoints. OpenFinance mapping: recharge events behave like financial operations that require traceable amount, status, and timestamp fields.

Scenario C: Multi-operator agency model

Business context: an agency runs several operator desks and needs strict role separation with central oversight.

Data/API involved: authentication, sub-account creation, and funding actions. OpenData mapping: identity and funding records become auditable governance data for internal policy enforcement.

Scenario D: Customer experience automation

Business context: support teams want proactive updates to reduce “where is my package?” and “did my top-up go through?” tickets.

Data/API involved: shipment status updates and recharge result polling. OpenData mapping: normalized event streams feed outbound notifications via email, SMS, or WhatsApp integrations.

Snippet 1: Auth token exchange

POST /api/v1/authentication
Content-Type: application/json
Accept-Language: en-US

{
  "username": "ops_user@example.com",
  "password": "********"
}

200 OK
{
  "accessToken": "eyJhbGciOi...",
  "iat": 1711000000,
  "exp": 1711003600,
  "user": {"id": 1982, "email": "ops_user@example.com"}
}

Snippet 2: Shipment rate + create flow

POST /api/v1/shipments/rates
Authorization: Bearer <token>
{
  "origin_country": "US",
  "destination_country": "CO",
  "weight_kg": 3.5,
  "category": "electronics"
}

POST /api/v1/shipments
{
  "service_id": "svc_2801",
  "recipient": {"name": "Ana Perez"},
  "package": {"weight_kg": 3.5}
}

Error handling:
- 401: refresh token and retry once
- 422: validation failure -> return field-level diagnostics

Snippet 3: Recharge write + status polling

POST /api/v1/mobile-recharges/recharges
Authorization: Bearer <token>
{
  "provider_id": "prov_ve_001",
  "product_id": "topup_20usd",
  "phone_number": "+58XXXXXXXXXX",
  "amount": 20.00,
  "client_reference": "INV-2026-00481"
}

GET /api/v1/mobile-recharges/recharges?from=2026-04-01&to=2026-04-30

Recommended controls:
- idempotency key on create
- daily export to ledger table
- immutable audit log for status transitions

Compliance & privacy

For cross-border shipping and recharge integrations, compliance is operational, not decorative. We implement data minimization, encryption-in-transit controls, and retention boundaries based on your geography. For LATAM and global delivery use cases, teams commonly align with Brazil LGPD when serving Brazilian users and GDPR where EU-linked processing occurs. If U.S. resident data is involved, privacy workflows can be aligned with state-level requirements such as California CPRA.

From public store disclosures, We Ship You indicates collection of location/contact/financial-linked categories and offers deletion request options. We reflect this in integration policy by defining explicit lawful-purpose fields and by documenting how data is pulled, transformed, and purged.

Data flow / architecture

A practical implementation pipeline is: Client app / operator portal → Ingestion API gateway → Normalized storage (shipments, recharges, accounts) → Output APIs and analytics exports. This four-node pattern keeps operational writes isolated from analytics reads and makes consent and retention policy easier to enforce.

When needed, we add a queue between ingestion and storage to absorb burst traffic during campaign windows or holiday shipping peaks.

Aeropost

Aeropost is a long-running cross-border shipping app in LATAM and the Caribbean. Teams integrating both Aeropost and We Ship You often need unified shipment export schemas and harmonized tracking event dictionaries.

EncargoGo

EncargoGo focuses on cross-border shopping and delivery to multiple LATAM destinations. In mixed environments, businesses typically normalize quote and final-delivery data to compare route economics.

Latinbits Cargo

Latinbits Cargo operates locker and forwarding workflows similar to We Ship You categories. Shared integration demand usually centers on consolidation status feeds and destination-country reporting.

Upper Express

Upper emphasizes U.S.-to-LATAM purchase forwarding with real-time status visibility. Companies working across both tools often request common SLA dashboards and exception-event APIs.

Remitly

Remitly is a major remittance app used by migrant communities that overlap with cross-border shipping users. Joint analytics projects commonly combine payout activity signals with shipment cadence for customer segmentation.

WorldRemit

WorldRemit provides international transfer and airtime pathways relevant to recharge-centric audiences. Integrators frequently need shared recipient identity and destination-country mapping across remittance and recharge rails.

Sendwave

Sendwave serves transfer corridors where instant payout and wallet usage matter. In broader ecosystem integrations, teams align transaction status models between shipping-service payments and remittance operations.

BOSS Revolution & MobileRecharge

These apps are prominent in international top-up workflows. Businesses handling We Ship You recharge operations often ask for a single top-up transaction export format that supports provider-level reconciliation across multiple platforms.

About our studio

We are a technical integration studio focused on authorized app interface integration and API delivery for fintech, logistics, and cross-border commerce. Our work combines protocol analysis, interface refactoring, OpenData pipeline design, and testable source-code delivery so your engineering team receives implementation artifacts instead of slideware.

Delivery includes API specs, runnable service modules, test scripts, and integration runbooks. Engagement can be source-code handover (from $300, pay after delivery satisfaction) or usage-based pay-per-call access on hosted endpoints.

Contact information

Share your target app name, required data points, and expected output format. We will scope protocol analysis and integration milestones quickly.

Go to contact page

Deliverables

• OpenAPI-style interface spec and endpoint mapping
• Auth/session model implementation (token lifecycle and refresh policy)
• Shipment, tracking, recharge, and funding API adapters
• Automated scripts for data extraction, transformation, and scheduled delivery
• Test plan (happy path, validation errors, retry behavior, and data integrity)
• Operational documentation for handover and production rollout

Workflow

1. Requirement alignment and data contract definition
2. Protocol analysis and endpoint behavior validation
3. Adapter implementation with sandbox/live environment support
4. Automated test and monitoring checklist delivery
5. Production handover, rollback plan, and support window

FAQ

What do you need to start?
Target app, expected business flows (for example shipment export or recharge status sync), and preferred output format such as REST, webhook, CSV, or warehouse table.

Can you support both Android and iOS contexts?
Yes. We support integration scenarios that originate from either platform as long as access is authorized and compliant.

Do you provide documentation for auditors and operations teams?
Yes. We provide field dictionaries, flow definitions, and error-handling behavior so engineering and compliance teams can review the same canonical artifacts.