Skip to content
Human resources ⇄ Accounting and finance

D2l Brightspace to Recurly integration — real-time, two-way sync

Keep D2l Brightspace and Recurly in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect D2l Brightspace and Recurly

Keep the employee, department, and cost records that Recurly and D2l Brightspace share consistent in real time, so the finance system and the people system stop drifting apart.

Recurly runs the money side of the company: who gets paid, what it costs, and which part of the business the cost belongs to. D2l Brightspace runs the people side: who works here, which team they sit in, and how their employment changes over time. The two overlap on the same people and the same org structure, because every employee is also a payee and every department is also a cost center. When that overlap is maintained by hand, a new hire, a transfer, or a termination has to be keyed twice, and the two systems start to disagree about who is active and where the cost lands.

Stacksync syncs Line Items, Coupons and Redemptions, Billing Info, Measured Units and Usage in Recurly with Org Units, Grades, Content (Modules, Topics, and User Progress), Quizzes in D2l Brightspace bi-directionally and in real time. A person added, updated, or deactivated on either side appears on the other within seconds, with field-level mapping and conflict resolution in place of CSV exports and nightly batch jobs.

That matters most when money follows a people event. A hire that finance can pay, a leaver whose access ends, a transfer that redirects cost to the right team, all happen from one change instead of two, so headcount and spend reconcile from the same set of records.

Common use cases

  • 01 Post usage records to Measured Units on metered Subscriptions from a metering database before each bill run.
  • 02 Sync Accounts and Subscriptions bi-directionally with Postgres so product and provisioning systems read live entitlement state and write plan or seat changes back to Recurly.
  • 03 Pull Content user progress and Quiz attempt results into a Postgres warehouse for engagement and completion analytics.
  • 04 Sync Assignment (Dropbox) submissions and feedback into a reporting database or downstream review tool.

Common sync patterns

Department and cost-center alignment

The org structure maintained in D2l Brightspace keeps the departments or cost centers in Recurly current, so spend and headcount roll up the same way.

Status changes propagate

A role, department, or employment-status change in either system updates the other within seconds, so cost allocation, access, and reporting reflect the current state.

People-driven costs land in finance

Compensation, reimbursements, or other costs tied to a person on the D2l Brightspace side flow into Recurly for posting, so the books reflect what people actually cost without manual re-entry.

What you can sync between D2l Brightspace and Recurly

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

D2l Brightspace objects Recurly objects How this pairing syncs
Content (Modules, Topics, and User Progress) Course content structure plus per-user completion; progress is read into a warehouse and topics can be created and updated via the API. Transactions Individual payment attempts — captures, refunds, and voids; typically read into a warehouse for reconciliation and dunning analysis. Content (Modules, Topics, and User Progress) is specific to D2l Brightspace and Transactions to Recurly — each maps to any object or custom field on the other side.
Quizzes Quiz objects and per-user attempts and results; attempt data is read out for engagement and completion analytics. Line Items One-time charges and credits on an account outside a subscription; synced for accurate revenue and adjustment reporting. Quizzes is specific to D2l Brightspace and Line Items to Recurly — each maps to any object or custom field on the other side.
Assignments (Dropbox) Dropbox folders, submissions, and feedback; submission and evaluation data is read into reporting systems and feedback can be written back. Coupons and Redemptions Discount definitions and their application to accounts and subscriptions; read for discount and promotion analysis. Assignments (Dropbox) is specific to D2l Brightspace and Coupons and Redemptions to Recurly — each maps to any object or custom field on the other side.
Groups and Sections Group categories, groups, and section membership within an org unit; enrollments are read and written to keep cohort assignments aligned. Billing Info Tokenized payment method (card/ACH) on an account; written when onboarding customers and read for payment-health signals (never stores raw card numbers). Groups and Sections is specific to D2l Brightspace and Billing Info to Recurly — each maps to any object or custom field on the other side.
Users User accounts in the Learning Platform (lp) component; created, read, updated, and deleted through the Valence API and typically synced two-way with an SIS or HRIS. Measured Units and Usage Metered-billing units; usage records are posted to a subscription before each bill run for consumption-based pricing. Users is specific to D2l Brightspace and Measured Units and Usage to Recurly — each maps to any object or custom field on the other side.
Enrollments Links between Users and Org Units; enroll/unenroll and batch-enrollment routes let rosters be written from an upstream system and read back for reporting. Accounts Customer/billing entity records keyed by account_code; the anchor most subscriptions and invoices hang off. Synced two-way with CRM accounts or a customer database. Enrollments is specific to D2l Brightspace and Accounts to Recurly — each maps to any object or custom field on the other side.

How changes propagate between D2l Brightspace and Recurly

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

D2l Brightspace Recurly Sub-second propagation

DetectionD2l Brightspace notifies Stacksync of record changes through webhook events. Polling Valence endpoints with date/bookmark filters, differential Brightspace Data Sets (BDS) bulk exports for changed rows via the Data Hub, and.

DeliveryEach detected change is written to Recurly through its API, with automatic retries and rate-limit backoff.

Recurly D2l Brightspace Sub-second propagation

DetectionRecurly notifies Stacksync of record changes through webhook events. Webhooks (JSON or XML, one format per endpoint) for account, subscription, payment, and invoice events, plus incremental polling of list endpoints.

DeliveryEach detected change is written to D2l Brightspace through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • D2l Brightspace: Per-caller token-bucket credit scheme; each route costs credits, responses carry X-Rate-Limit-Remaining, and over-quota calls return HTTP 429. D2L can adjust per-route credit costs.
  • Recurly: Production sites default to 1,000 requests/min with only GET requests counting toward the limit; sandbox sites 400/min with all requests counting; the limit is a sliding 5-minute window, X-RateLimit headers report the quota, and breaches return HTTP 429.
What ships with D2l Brightspace ⇄ Recurly

Connect D2l Brightspace and Recurly for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every D2l Brightspace–Recurly connection.

Real-time

Two-way sync

Changes in D2l Brightspace or Recurly instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever D2l Brightspace or Recurly data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single D2l Brightspace or Recurly record.

Observability

Monitoring

Track your D2l Brightspace ⇄ Recurly sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between D2l Brightspace and Recurly.

How the D2l Brightspace and Recurly connectors work

D2l Brightspace

Integration surface
Brightspace (Valence) REST API split into independently-versioned Learning Platform (lp) and Learning Environment (le) components, plus the Data Hub / Data Export Framework and Brightspace Data Streams
Authentication
OAuth 2.0 authorization-code grant against the D2L auth service (auth.brightspace.com); a registered app holds a client ID and secret with per-scope grants (group:resource:action, e.g. users:userdata:read), short-lived access tokens, and refresh tokens
Change detection
Polling Valence endpoints with date/bookmark filters, differential Brightspace Data Sets (BDS) bulk exports for changed rows via the Data Hub, and Brightspace Data Streams webhooks (xAPI activity events) for near-real-time signals
Capabilities
read · write · webhooks
Rate limits
Per-caller token-bucket credit scheme; each route costs credits, responses carry X-Rate-Limit-Remaining, and over-quota calls return HTTP 429. D2L can adjust per-route credit costs.
D2l Brightspace setup guide

Recurly

Integration surface
REST API (V3, date-versioned; legacy V2 XML API also exists)
Authentication
API key via HTTP Basic auth (key as username, blank password); keys are per-site, with separate sandbox and production keys
Change detection
Webhooks (JSON or XML, one format per endpoint) for account, subscription, payment, and invoice events, plus incremental polling of list endpoints sorted by updated_at with begin_time/end_time filters
Capabilities
read · write · webhooks
Rate limits
Production sites default to 1,000 requests/min with only GET requests counting toward the limit; sandbox sites 400/min with all requests counting; the limit is a sliding 5-minute window, X-RateLimit headers report the quota, and breaches return HTTP 429.
How it works

How to connect D2l Brightspace to Recurly — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate D2l Brightspace and Recurly with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    D2l Brightspace connected
    Recurly connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the D2l Brightspace and Recurly objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · D2l Brightspace ⇄ Recurly
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    D2l Brightspace Recurly
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

D2l Brightspace and Recurly integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 398 integrations available for D2l Brightspace and Recurly.

Popular · 6 of 398
All D2l Brightspace integrations All Recurly integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own