Showing results for 
Search instead for 
Did you mean: 
Advocate I
Advocate I

Connecting Custom API

Hi everyone!


I've been tryong to connect NASA APOD's API in PowerApps but I've been receiving an error everytime I call my connector:


My get:

RequestRequestResponse I getResponse I get

Now I'm confused, what is causing this error to come up and why I cant pull down the data from API? Some were sucessful when they pulled in the data via flows, but now as a custom connector, it cannot work? Appreciate everyone's response 🙂 

Super User
Super User

Hi @zdames

What property are you trying to set here? For instance, are you trying to show the result of the API call in a gallery or in a label?

If you add a button to your screen, can you successfully ClearCollect the API call to a new collection, and view the collection from the designer?


Community Support
Community Support

Hi @zdames,

Which Response type do you specify within your Open API definition file?

Could you please share more details about the Open API definition file of your custom connector?

Based on the error message that you provided, it seems to tell that the property (query parameter) of the control is required to provide a Table value, but your custom connector formula return a Text value.

Based on the Response screenshot that you provided, I think you have defined your Response type as Object within your OpenAPI definition file, is it true?

Please consider take a try to define your Response type as array within your OpenAPI definition file as below:

  "swagger": "2.0",
  "info": {
    "version": "1.0.0",
    "title": "SentimentDemo",
    "description": "Uses the Cognitive Services Text Analytics Sentiment API to determine whether text is positive or negative"
  "host": "",
  "basePath": "/",
  "schemes": [
  "consumes": [],
  "produces": [
  "paths": {
    "/text/analytics/v2.0/sentiment": {
      "post": {
        "summary": "Returns a numeric score representing the sentiment detected",
        "description": "The API returns a numeric score between 0 and 1. Scores close to 1 indicate positive sentiment, while scores close to 0 indicate negative sentiment.",
        "operationId": "DetectSentiment",
        "parameters": [
        "responses": {
          "200": {
            "description": "200",
            "schema": {
              "type": "array",  /* <-- Modify here. Change the Response type from object into array */
              "properties": {
                "documents": {
                  "type": "array",
                  "items": {
                    "type": "object",
                    "properties": {
                  "description": "documents",
                  "x-ms-summary": "documents"
  "definitions": {},
  "parameters": {},
  "responses": {},
  "securityDefinitions": {
  "security": [],
  "tags": []

then re-create a new custom connector based on your OpenAPI definition file, check if the issue is solved.

Please also check and see if the following thread would also help in your scenario:


Best regards,


Community Support Team _ Kris Dai
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Not applicable

Thanks for your help with this thread @timl and @v-xida-msft


@zdames if you're still receiving this error, can you review the information provided and reply in this thread?



Helpful resources

Power Platform Conf 2022 768x460.jpg

Join us for Microsoft Power Platform Conference

The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.

May UG Leader Call Carousel 768x460.png

June User Group Leader Call

Join us on June 28 for our monthly User Group leader call!

PA Virtual Workshop Carousel 768x460.png

Register for a Free Workshop

This training provides practical hands-on experience in creating Power Apps solutions in a full-day of instructor-led App creation workshop.


New Release Planning Portal (Preview)

Check out our new release planning portal, an interactive way to plan and prepare for upcoming features in Power Platform.

Top Solution Authors
Users online (1,382)