BeMob Actions
Read and manage campaigns, offers, landing pages, flows, traffic sources, and affiliate networks in your BeMob account directly from AffZero automations.
Overview
AffZero provides a set of Tracker Actions for BeMob that let you query and update your account without logging into the BeMob UI. All actions run against the BeMob REST API (api.bemob.com) and require a configured BeMob connection.
BeMob uses UUID strings for all entity IDs (campaigns, offers, landing pages, flows, traffic sources, affiliate networks) — they look like 3fa85f64-5717-4562-b3fc-2c963f66afa6. Use a Get All action first to discover the IDs you need.
Every object below supports the exact same six actions, since BeMob's REST API is uniform across object types.
Campaign Actions
Get All Campaigns
Retrieve campaigns in your BeMob account, with optional filters.
Parameters: Status (active/archived), Workspace IDs, Traffic Source IDs, Updated From/To, Limit, Offset.
Use this to: Look up a campaign UUID before using Get Campaign or Edit Campaign.
Get Campaign
Retrieve full details for a single campaign by ID.
Parameters: Campaign ID (required).
Create Campaign
Create a new campaign via POST /campaigns.
Required fields: Name, Traffic Source ID.
Optional fields: Workspace ID, Status, Destination Type (flow or url), Flow ID, Destination URL, Cost Model, Cost Value, Currency, Redirect Mode, Tracking Domain ID, Redirect Domain ID, Inline Flow Rules (JSON), and an Advanced Fields JSON object for less-common fields (e.g. trafficLossPercent, uniquenessPeriod, sendCustomEventPostback).
A campaign routes traffic either through a saved Flow (flowId) or an inline rule set (flowInline) with the same rules/conditions/paths structure a Flow uses. Load an existing campaign or flow first to see the current JSON shape before writing your own.
Edit Campaign
Update a campaign's configuration. AffZero fetches the current campaign state after writing and flags any field BeMob silently didn't apply.
Parameters: Campaign ID (required) + any of the Create Campaign fields to update.
Archive / Restore Campaigns
Archive or restore one or more campaigns in a single call.
Parameters: Campaign ID(s) (required, comma-separated for multiple).
Update Campaign Cost
Update a campaign's cost for a time range, optionally restoring the previous value.
Parameters:
| Field | Required | Description |
|---|---|---|
| Campaign ID | Yes | The BeMob campaign UUID |
| Cost | Yes | Cost amount to record |
| Currency | No | e.g. USD |
| Start/End Timestamp | No | ISO datetime range the cost applies to |
| Restore Previous Value | No | Revert to the prior cost value instead of applying a new one |
Bulk Update Campaigns
Update multiple campaigns at once with the same field changes — one confirmation instead of N.
Parameters:
| Field | Required | Description |
|---|---|---|
| Workspace ID | Yes | The workspace the campaigns belong to |
| Campaign IDs | Yes | Comma-separated campaign UUIDs (max 100) |
| Field Changes (JSON) | Yes | JSON object of fields to apply to every campaign, e.g. { "costValue": 0.5, "costModel": "cpc" } |
Count Campaigns
Returns the total number of campaigns in the account. No parameters.
Offer Actions
Get All Offers / Get Offer
List offers (filters: Status, Search, Workspace IDs, Order By/Direction, Limit, Offset) or retrieve a single offer by ID.
Create / Edit Offer
Required fields (create): Name, URL.
Optional fields: Workspace ID, Payout Type, Payout Sum, Click ID Param, Country ID, Currency, Affiliate Network ID, Enable Daily Cap, Daily Cap Limit, Daily Cap Timezone, Daily Cap Failover Offer ID.
Edit uses the same fields, plus a required Offer ID — only the fields you set are changed.
Archive / Restore Offers
Archive or restore one or more offers by ID.
Landing Page Actions
Get All Landing Pages / Get Landing Page
List landing pages (filters: Status, Search, Off Tags, Order By/Direction, Limit, Offset) or retrieve one by ID.
Create / Edit Landing Page
Required fields (create): Name, URL.
Optional fields: Workspace ID, Country ID, Linked Offers (count).
Archive / Restore Landing Pages
Archive or restore one or more landing pages by ID.
Flow Actions
Flows hold the routing rules (conditions + paths of landing pages/offers) that a campaign can point to instead of a single destination URL.
Get All Flows / Get Flow
List flows (filters: Status, Workspace IDs, Limit, Offset) or retrieve one by ID.
Create / Edit Flow
Required fields (create): Name.
Optional fields: Workspace ID, Country ID, Rules (JSON array) — the same { name, default, status, conditions, paths } structure used by a campaign's inline flow.
Archive / Restore Flows
Archive or restore one or more flows by ID.
Traffic Source Actions
Get All Traffic Sources / Get Traffic Source
List traffic sources (filters: Status, Workspace IDs, Limit, Offset) or retrieve one by ID.
Create / Edit Traffic Source
Required fields (create): Name.
Optional fields: Workspace ID, Postback URL, Track Impressions, External Click ID Param/Placeholder, Cost Param/Placeholder, Traffic Loss %, Use Custom Params, Use Traffic Loss, Integration ID, Integration Cost Estimation, and an Advanced Fields JSON object for the custom1–custom10 macro slots.
Archive / Restore Traffic Sources
Archive or restore one or more traffic sources by ID.
Affiliate Network Actions
Affiliate Networks are BeMob's term for offer sources — the network you get offers from, not a traffic-buying affiliate.
Get All Affiliate Networks / Get Affiliate Network
List affiliate networks (filters: Status, Workspace IDs, Limit, Offset) or retrieve one by ID.
Create / Edit Affiliate Network
Required fields (create): Name.
Optional fields: Workspace ID, Status, Click ID Param, Append Click ID, Postback Whitelisted IPs, Postback Only From Whitelisted IPs, Accept Double Postbacks, Template ID, Use Postback Statuses, Default Postback Status, and the per-status Postback Status Param overrides (New/Confirm/Decline/Chargeback).
Archive / Restore Affiliate Networks
Archive or restore one or more affiliate networks by ID.
Tips for BeMob Users
- UUIDs, not numbers — BeMob entity IDs are UUID strings, not short integers like Binom. Use the Get All actions to look up the correct UUID before referencing it in edit or get actions.
- Get before Edit — AffZero automatically verifies an edit by re-fetching the object afterward, but running a Get action first in the same automation lets you use the retrieved data as variables in the edit step.
- JSON fields — Inline Flow Rules, Rules, and the various Advanced Fields parameters take a raw JSON object/array. Load an existing campaign/flow/object first to see the current structure before writing your own.
- Workspaces — most objects can be scoped to a Workspace ID; omit it to use your account's default workspace.