Integration Specifications

This article will help you learn about how Daasity replicates data from Aspire, limitations to the data we can extract and where the data is stored in the Aspire schema

Integration Overview

Aspire is an influencer marketing platform for e-commerce brands, allowing merchants to build a network of influencers and manage their ROI performance, content creation, and digital marketing strategies.

This document provides context on what kind of data is being gathered through this extractor, which endpoints that data is coming from, and how the extracted tables relate to each other

Integration Availability

This integration is available for:

  • Enterprise

API Endpoints

The Daasity Aspire extractor is built based on this Aspire API documentation. The following endpoints are used by Daasity to replicate data from Aspire:

Entity Relationship Diagram (ERD)

Click here to view the ERD for the Daasity Aspire IQ integration illustrating the different tables and keys to join across tables.

Aspire Schema

The Daasity Aspire extractor creates these tables using the endpoints and replication methods listed. The data is mapped from source API endpoint to the table based on the mapping logic outlined in each table.

Posts

  • Endpoint: Posts

  • Update Method: UPSERT

  • Table Name: [aspireiq.posts]

Last updated