Quora Ads

Navigate to quora.com/business/advertising-api and submit your application for API partner access. Quora reviews applications manually — approval timelines vary and are not publicly stated. During your application, be specific about your use case (e.g., 'building a no-code analytics dashboard for Quora Ads in Bubble to pull campaign metrics without logging into Ads Manager'). While you wait for approval, use this time productively: design your Bubble app's reporting UI with placeholder data, create the Data Types you'll need (e.g., 'QuoraCampaign' with fields like campaign_id TEXT, name TEXT, status TEXT, daily_spend NUMBER, clicks NUMBER, impressions NUMBER), and set up your App Config Data Type with fields for the access_token and refresh_token. When approval arrives, Quora provides API documentation through their partner portal — the base URL and endpoint paths are documented there. This brief provides the most likely base URL (https://www.quora.com/api/v1) but always use the official partner documentation as your source of truth, as endpoints may have changed.

Once Quora approves your partner application, you receive a Client ID and Client Secret along with API documentation. Follow the OAuth 2.0 flow specified in the partner docs — Quora supports either a client credentials flow (simpler, if your use case is account-level reporting for your own account) or an authorization code flow (if building a multi-tenant tool where end-users authorize their own Quora accounts). For a single-account reporting dashboard (the most common Bubble use case), the client credentials flow works as follows: send a POST request to Quora's token endpoint with your Client ID and Secret, and receive an access token in the response. Use a REST client like Insomnia or Postman for this step since Bubble's API Connector is not well-suited for one-time token exchanges. Copy the access token and any refresh token from the response, and store them in your Bubble App Config Data Type (the fields you created in Step 1). The access token goes into the API Connector header, and the refresh token is kept in your database for automated renewal. Refer to Quora's partner documentation for the exact token endpoint URL and required parameters, as these are provided upon approval and may differ from what is shown in public resources.

1// Conceptual structure for Quora OAuth token request
2// Refer to your partner portal documentation for the exact endpoint
3
4// POST [quora_token_endpoint_from_partner_docs]
5// Content-Type: application/x-www-form-urlencoded
6
7// Body:
8grant_type=client_credentials
9&client_id=YOUR_CLIENT_ID
10&client_secret=YOUR_CLIENT_SECRET
11
12// Expected response structure (verify against partner docs):
13{
14  "access_token": "your_access_token_here",
15  "token_type": "bearer",
16  "expires_in": 3600,
17  "refresh_token": "your_refresh_token_here"
18}

In your Bubble editor, go to the Plugins tab in the left sidebar and click Add plugins. Search for API Connector — the official plugin by Bubble — and install it. Click API Connector in your installed plugins list, then click Add another API. Name the group Quora Ads. In the Shared headers section, click Add a shared header. Set the key to Authorization, set the value to Bearer YOUR_ACCESS_TOKEN, and check the Private checkbox to the right. This is the critical security step: the Private flag tells Bubble's servers to keep this header value away from any client-side context — your token is never sent to the browser and cannot be extracted by users of your Bubble app. Set the base URL to https://www.quora.com/api/v1 (or the base URL provided in your partner documentation if it differs). Add a second shared header: key Content-Type, value application/json (no Private flag needed here). Click Expand to create your first API call.

1// API Connector group: Quora Ads
2// Base URL: https://www.quora.com/api/v1 (verify against partner docs)
3
4// Shared headers:
5{
6  "Authorization": "Bearer YOUR_ACCESS_TOKEN",  // <-- mark Private
7  "Content-Type": "application/json"
8}

Within the Quora Ads group, click Add a call. Name it Verify Auth and Get Account. Set the method to GET and the endpoint to /accounts/YOUR_ACCOUNT_ID (replace YOUR_ACCOUNT_ID with your actual Quora Ads account ID, which is provided in your partner documentation or visible in the Quora Ads Manager URL). Click Initialize call — Bubble makes a live request and needs a successful response to detect the field schema. If the Initialize returns an error, verify that your access token has not expired and that the Authorization header is formatted correctly (Bearer followed by a space and then the token, with the Private checkbox checked). When the initialize succeeds, Bubble shows the detected fields from the account response. This confirms your auth is working. Next, add a second call named Get Campaigns. Set the method to GET and the endpoint to /accounts/YOUR_ACCOUNT_ID/campaigns. Initialize this call too — Bubble detects the campaign fields including campaign IDs, names, and status values. Set Use as to Data. Note the campaign ID field from the response — you will use it as a path parameter in the analytics call. The campaign and analytics data structures are separated by Quora's API design, so you need both calls and will join them in your Bubble workflows.

1// Call 1: Verify Auth
2// GET /accounts/{account_id}
3// Full URL: https://www.quora.com/api/v1/accounts/YOUR_ACCOUNT_ID
4
5// Call 2: Get Campaigns
6// GET /accounts/{account_id}/campaigns
7// Full URL: https://www.quora.com/api/v1/accounts/YOUR_ACCOUNT_ID/campaigns
8
9// Expected campaign list response structure:
10{
11  "data": [
12    {
13      "id": "campaign_abc123",
14      "name": "Brand Awareness Q1",
15      "status": "ACTIVE",
16      "daily_budget": 100.00,
17      "start_date": "2024-01-01"
18    }
19  ]
20}

Add a third call named Get Campaign Metrics. Set the method to GET and the endpoint to /accounts/YOUR_ACCOUNT_ID/campaigns/CAMPAIGN_ID/metrics (using path parameters, or using a call-level URL parameter for campaign_id). Add URL parameters for start_date and end_date (format: YYYY-MM-DD per partner documentation) and optionally a granularity parameter (DAY or WEEK). Click Initialize call using a known date range during which your campaign was active. Once initialized, Bubble shows the metric fields — expect fields like spend, clicks, impressions, conversions, and cpa depending on what Quora's API returns for your account. Now build the Bubble UI: add a Repeating Group to your campaign analytics page, set its Type of content to Quora Campaign (your Data Type) or to the API call's result type. Add a date range input above the Repeating Group using two Date Picker elements. In the Repeating Group's workflow (or in the Page Load workflow), use a Make API call action to call Get Campaigns, then loop through results to call Get Campaign Metrics for each campaign ID. Display spend, clicks, impressions, and CPA in cells within the Repeating Group. For privacy: go to Data tab → Privacy, find your QuoraCampaign Data Type, and ensure only admin users (or no public roles) can see the stored data — campaign spend and CPA figures should not be publicly accessible.

1// GET /accounts/{account_id}/campaigns/{campaign_id}/metrics
2// Full URL example:
3// https://www.quora.com/api/v1/accounts/YOUR_ACCOUNT_ID/campaigns/campaign_abc123/metrics
4
5// URL Parameters:
6{
7  "start_date": "2024-01-01",
8  "end_date": "2024-01-31",
9  "granularity": "DAY"
10}
11
12// Expected response (verify against partner docs):
13{
14  "data": [
15    {
16      "date": "2024-01-15",
17      "spend": 45.30,
18      "clicks": 112,
19      "impressions": 8420,
20      "conversions": 8,
21      "cpa": 5.66
22    }
23  ]
24}

OAuth access tokens have limited lifespans — typically hours to days depending on Quora's configuration for your partner account. Without a refresh mechanism, your Bubble dashboard will stop working when the token expires and require manual intervention. On a paid Bubble plan, build a Backend Workflow to handle this automatically. Go to Settings → API in Bubble and enable 'This app exposes a Workflow API'. Navigate to Backend Workflows and create a new workflow named 'Refresh Quora Token'. In the API Connector, add a new call named Refresh Token — set it to POST with the token refresh endpoint from your Quora partner documentation (the endpoint accepts the refresh_token and returns a new access_token). Add this as an API Connector call with the client credentials in the body or header as specified in your partner docs. In the Backend Workflow, add two actions: (1) Make API call → Refresh Token, passing the refresh_token from your App Config Data Type; (2) Make changes to Thing → update App Config's access_token field with the new token from the API response. Set up a recurring event under Backend Workflows to run this workflow on a schedule matching your token's lifespan (e.g., every hour if the token expires hourly, or every 20 hours for a 24-hour token). If you need help structuring the token refresh flow or the chained campaign → metrics calls, RapidDev has built hundreds of Bubble integrations like this — book a free scoping call at rapidevelopers.com/contact.

1// Backend Workflow: Refresh Quora Token
2// Trigger: Recurring event (set interval to match your token expiry)
3
4// Action 1: Make API call → Refresh Token
5// POST [quora_token_endpoint]
6// Body: { grant_type: 'refresh_token', refresh_token: App Config's refresh_token }
7
8// Action 2: Make changes to App Config
9// Field: access_token = Result of Step 1's access_token
10
11// Note: requires paid Bubble plan for Backend Workflows + recurring events