Ongoing + Sendify
Everything you need to connect Ongoing and Sendify: how to connect, which data moves, which settings there are and what to do when something goes wrong.
- 1 data flow
- Connect in about 13 minutes
1. Getting started
Prepare both systems first, then connect them in Junipeer.
- about 10 minutes
Prepare Ongoing
- Open the Ongoing API access setup
- Create or confirm the dedicated API user
- Copy the API username and password
- Confirm any client or goods owner identifiers
- Paste the credentials into Junipeer
- about 3 minutes
Prepare Sendify
- Log in to Sendify
- Open the API settings page
- Retrieve the API key
- Paste the key into Junipeer
Connect and test
Enter the details in Junipeer, switch on the flows you need and test with one order before you go live.
Getting started with Junipeer
2. How the data flows
What Junipeer can move between the two systems. The arrow shows which way the data goes.
Junipeer - Orders
3. Settings
The settings you see in Junipeer, in plain words. Open one to read more. The key is the technical name.
You don't need to read them all
In Junipeer every setting has a ? that opens the same explanation next to the form, right when you need it. With the Junipeer MCP your AI assistant can also propose the settings from your own data.
How the Junipeer MCP worksSettings for Ongoing (2)
| Setting | What it controls | Key |
|---|---|---|
| Exclude Orders created before this date | Pick a date to skip older orders. | stdintegration_filter_ongoing_order_created_date |
| Goods owner | Choose which Ongoing goods owner this integration works with. | ongoing_goods_owner_id |
Settings for Sendify (36)
| Setting | What it controls | Key |
|---|---|---|
| Address Line 1 | The first line of the address, usually the street and number. | address_line_1 |
| Address Line 2 | An extra address line, if the address needs one. | address_line_2 |
| Address Line 3 | A third address line, if the address needs one. | address_line_3 |
| Api Key | Enter the API key for your Sendify account. | sendify_api_key |
| Carrier Accounts | Connect each carrier with your own account identifier at that carrier. | carrier_accounts |
| City | The city of the address. | city |
| Contact Email | The e-mail address of the contact. | contact_email |
| Contact Name | The name of a contact person. | contact_name |
Show all 36 settings
| Setting | What it controls | Key |
|---|---|---|
| Contact Phone | The phone number of the contact. | contact_phone |
| Country Code | The country of the address, written as a two-letter country code – for example SE , NO or DK . | country_code |
| Default Generated Package Weight (kg) | The weight to use when Junipeer generates packages and there is no package or item weight to go on. | sendify_default_generated_weight_kg |
| Default Package Key | The package template to use when Junipeer needs to generate packages because the shipment has no parcels. | sendify_default_package_template_key |
| Default Sender | Choose which sender is used by default when shipments are sent to Sendify. | sendify_default_sender_key |
| Default Weight (kg) | The weight to use when a parcel has no weight , in kilograms. | default_weight_kg |
| Depth (cm) | The depth of the package, in centimeters . | depth_cm |
| Description | A default description of the package. | description |
| Enable Bookable Validation | Decide whether Junipeer should check that a shipment can actually be booked when it is created in Sendify. | sendify_enable_bookable_validation_mode |
| Height (cm) | The height of the package, in centimeters . | height_cm |
| Map Package Types to Package Templates | Use a specific package template for each package type in Specter. | sendify_map_parcel_type_to_template |
| Map Warehouses to Sender | Use a different sender depending on which Specter warehouse the shipment comes from. | sendify_map_warehouse_to_sender |
| Max Weight Per Package (kg) | The highest weight one package may have, in kilograms. | max_weight_per_package_kg |
| Name | Enter the name for this entry – for example the company or warehouse name of a sender. | name |
| Order shipping address source | Choose which address on the order is used as the destination in Sendify. | sendify_order_shipping_address_source |
| Package Type | Choose the package type to use, for example PACKAGE . | type |
| Packages | Set up package templates – standard package sizes and weights – that you can reuse when packages are mapped or generated. | sendify_package_templates |
| Postal Code | The postal code (zip code) of the address. | postal_code |
| Province or State | The province or state of the address, for countries that use one. | province |
| Receiver Reference Source | Choose what is used as the receiver reference on the shipment in Sendify. | sendify_receiver_reference_source |
| Require Packages | Decide what happens when a shipment has no packages. | sendify_require_packages |
| Sender Reference Source | Choose what is used as the sender reference on the shipment in Sendify. | sendify_sender_reference_source |
| Senders | Set up the senders (return addresses and contact details) you want to use for shipments in Sendify. | sendify_senders |
| Shipping Method Field | Choose which Sendify value is used as the shipping method on shipments sent to the other system. | sendify_shipping_method_field |
| Stackable | Decide whether the package can be stacked . | stackable |
| Test Mode | Decide whether Junipeer sends to Sendify in test mode. | sendify_test_mode |
| Tracking Value Field | Choose which Sendify value is sent to the other system as the tracking information. | sendify_tracking_value_field |
| Width (cm) | The width of the package, in centimeters . | width_cm |
Did this page help you?