This article helps you identify, understand, and resolve common issues when integrating Power BI with Fastmarkets APIs. It covers Fastmarkets‑specific API errors, Power BI‑specific issues, and known limitations, with practical guidance on how to fix problems quickly.

How to Think About Errors in Power BI Integration?

When something breaks, the root cause usually falls into one of these categories:

• Instrument access issues (entitlements, incorrect symbols)
• Request construction issues (missing or invalid parameters)
• Authentication problems (rate limits, expired keys, wrong service name)
• Power BI configuration issues (privacy levels, connector prompts, outdated versions)

Many Fastmarkets API errors are returned with HTTP 200 OK, but contain inline error objects. Power BI may still treat these as successful calls unless you explicitly check the response payload. Always inspect the JSON response for invalidInstruments.

Fastmarkets API - Common Errors & How To Fix Them

200 OK with inline Forbidden

Cause: Your API account does not have access to the requested instrument.

"invalidInstruments": [
        {
            "symbol": "FP-PLP-0001",
            "error": "Forbidden",
            "message": "You do not have access to instrument 'FP-PLP-0001'."
        }
    ]

This happens when your API key is not entitled to requested dataset.

How to fix:

• Verify instrument entitlement in your Fastmarkets contract and ask Fastmarkets support to restore your access
• Remove restricted instruments from your Power BI query.

200 OK with Inline NotFound

Cause: The instrument symbol does not exist or is mistyped.

"invalidInstruments": [
        {
            "symbol": "FP-PLP-0001123",
            "error": "NotFound",
            "message": "Instrument 'FP-PLP-0001123' does not exist."
        }
    ] 

This happens when there's a typo in symbol or the symbol is outdated/decomissioned. The same error might appear in Market Data API or in News API for invalid Article ID.

How to fix:

• Validate symbols against official Fastmarkets documentation
• Avoid manual symbol entry where possible
• Centralise instrument lists as Power BI parameters

400 Bad Request - Missing Required Parameter 

Cause: A mandatory query parameter is not included.

 "invalidParameters": [
        {
            "parameter": "Ids",
            "error": "Missing",
            "message": "Missing required parameter 'Ids'"
        }
    ]

Why this happens:

• Query built dynamically in Power Query (M)
• Parameter name is case‑sensitive
• Empty value passed from a Power BI parameter

How to fix:

• Confirm required parameters for the endpoint
• Validate parameter values before executing the request
• Add defensive checks in M code (e.g. prevent empty lists)

Authentication 400 Bad Request - Invalid credentials

Cause: Incorrect credentials provided in the authentication request.

This happens on misspelling service name or service key. Please copy credentials directly from source and test authentication independently before using Power BI (cURL check, Postman etc.).

Authentication 400 Bad Request - Authentication Rate Limit

Cause: Too many authentication requests in a short time.

{
    "error": "invalid_request",
    "error_description": "You have exceeded the maximum number of 10 authentication requests within 5 minutes. Please try again later"
}

Why this happens:

• Refreshing credentials inside multiple Power BI queries
• Token request embedded directly in each query
• Frequent dataset refreshes during development

How to fix:

• Authenticate once and reuse the token across queries: check Power BI Connection approach
• Avoid calling the auth endpoint inside row‑level logic
• During development, disable unnecessary auto‑refreshes

401 Unauthorized - Get Data Fails

Possible causes:

• Required API scope is missing 
• Token expired and not refreshed

How to fix:

• Verify scopes for the specific API (Physical Prices vs News vs Market Data)
• Regenerate API key if expired
• Ensure token refresh logic is in place

Power BI-Specific Issues & Fixes

“Please Specify How to Connect” Error

Cause: Power BI cannot reconcile data sources due to privacy level conflicts or inconsistent authentication handling.

How to Fix:

1. In Power BI Desktop, go to File → Options and settings → Data source settings
2. Select each Fastmarkets API endpoint - Authentication and Data endpoints
3. Click Edit Permissions for each source
4. Set Privacy level to the same value (recommended: Organizational)
5. Apply and close
6. Restart Power BI Desktop

Additional checks:

• Use the latest Power BI Desktop version
• Ensure all API calls use the same base URL
• Avoid mixing anonymous and authenticated calls

Other common Power BI Errors

Troubleshooting Checklist

• Verify instrument entitlement
• Confirm instrument symbols
• Check required query parameters
• Avoid repeated authentication calls
• Align Power BI privacy levels
• Inspect JSON responses for inline errors