Skip to main content
To homepage To homepage

REST APIs

Ask questions about connecting to Rest APIs within TimeXtender

  • 51 Topics
  • 350 Replies
51 Topics
L
Contributor
Leo RogemanContributor
asked in REST APIs
MixPanel TX Rest API JSONL

Hi, I’m trying to connect to a API using Timextender REST version 7.1.0.0 but my result is only one row of data. In Postman I get much more data. It might be because the API returns JSONL and TX tries to handle it as JSON. I’m trying to convert it to Text but it still doesn’t work.  Earlier I managed to complete the goal in Power Query even with pagination.  Now I’ve hit a brick wall and I need your help to proceed. My result in ODX:  My result in Postman:Here’s my connection profile:{  "Name": "MixPanel",  "Description": "",  "Provider": {    "TemplateId": "d4aa4001-fd7b-4c65-b76d-f9710d551c1e",    "DisplayName": "TimeXtender REST",    "ProviderVersion": "7.1.0.0",    "X64BitVersion": true,    "ProviderType": 6  },  "RestProperties": {    "Pills": [      {        "Name": "Authentication",        "Description": "Configure authentication settings to securely access the API using tokens, keys, or other credentials.",        "Id": "rest-general-authentication",        "IsSelected": true 

4411
L
Contributor
L
Participant
luuk.boumanParticipant
asked in REST APIs
Almost empty records on API endpoint call

Hi,We're observing strange behavior with the new enhanced REST data source provider.When we do the call on this endpoint in the old connector or in Postman, we get a return of 197 records. This is a single payload, 1 page, with fully filled rows, including a populated PK field.Now, when we do the same call with the enhanced REST data source provider we receive 589 records. 392 of these have null values on all records except for one field, a descriptive but not otherwise important. Importantly the PK field of these records is also null.Now we have two questions: Why is the new REST provider delivering more records than other providers/tools? How can we effectively filter out these records in the actual call? As it seems we are now only able to successfully filter out these almost empty records at the DSA.Best, Luuk 

7614
L
Participant
J
Contributor
juriaan.hensbroekContributor
asked in REST APIs
TX Rest Dynamic value Endpoint query

I'm using dynamic values function in the TX REST connector 9.1.0.0. I use id's from another endpoint to loop through in my second endpoint path. This works well when I use “From Endpoint Table” but now I want to add a filter to only get the id's with a flag “hasresponse=true”.I've read the page but I still get an error with my Endpoint query. “No such table” the error message says. I've tried several things like adding a schema. But all with the same response. Is there something wrong with my syntax?Error: 

24618
J
Contributor
J
Starter
JDDOmniStarter
asked in REST APIs
Converting CDATA AD connector to Timextender REST

Hi,I've got a couple of installations with customers using CDATA for AD/Entra integration, with the upgrade I found an article to advise moving them to REST.I am however a bit lost on how to connect a REST API to Entra, and I couldn't find good documentation to fill it in.Could someone assist us for a moment or maybe point us toward more complete documentation specifically on using the Enhanced Data Source to connect to Entra?  Thanks in advance, Jan DD

182
J
Starter
Pontus Olausson
Contributor
Pontus OlaussonContributor
asked in REST APIs
How to Handle 400 Errors in TimeXtender REST Data Source with Dynamic Values?

Hi,We are using a REST data source with dynamic values to fetch data for approximately 12,000 records, where each record corresponds to an individual API call.Occasionally, we encounter issues with the API provider where some calls return a 400 error. Unfortunately, it’s unpredictable which dynamic values will cause these errors.Currently, it appears that the TimeXtender REST data source stops processing upon encountering a 400 error, resulting in a "Completed with errors" status.Is there a way to configure the REST data source to continue processing the remaining dynamic values, skipping over those that result in a 400 error? Ideally, it would also log the calls that failed for review. Best regards,Pontus

1156
J
Contributor
R
Starter
Robbert_TStarter
asked in REST APIs
Pagination for REST API Azure active directory

Hi,I'd like to make a new data source connection using REST to connect with our Azure storage table.Thus far I have managed to get the connection setup, however pagination remains a issue.When testing our connection and following the steps in the debug logging file I see that when a table has a next: "x-ms-continuation-NextPartitionKey” and "x-ms-continuation-NextRowKey” it will return this in the header (not the body). But if the table doesn't have this it will stop since the "x-ms-continuation-NextPartitionKey” header was not found.As I am applying these pagination parameters as query parameter I need to be able to solve this issue.Is there maybe a way to apply a default value to these variables (manipulating query doesn't work as the variable itself already won't be found) or some way to dynamically replace a URL? Example table with no NextPartition/rowkey:When variable value replaced with default:Thanks for any input someone can provide.Kind regards,Robbert

744
R
Starter
hugo.winkelhorst
Participant
hugo.winkelhorstParticipant
asked in REST APIs
Add a dynamic value to a table flattening of a REST API

Is it possible to add the dynamic values used in a nested call to a table flattening.In this particular case the first call gets the list of documents and feed the id as a dynamic value to the 2nd call. The response doesn't include any reference to the document and without the id we cannot link the details to a document. I've tried to add it as a static node (name: Document_ID  value {id})but that only results in errors.  

1189
Thomas Lind
Community Manager
J
Visitor
Joop van der LindenVisitor
posted in REST APIs
Json data, using GraphQl connector, return an error.

I need some help retrieving JSON data via GraphQl.When testing the connection in TimeXtender, I got a "Connection OK" message.After Synchronizing Data Source in TimeXtender an error message is displayed :   System.Data.CData.GraphQL.GraphQLDataReader ExecuteDataReader(System.Data.CommandBehavior)  [500] Could not execute the specified command: The defined query is null. : "UserViews"."query"  System.Data.CData.GraphQL.GraphQLDataReader ExecuteDataReader(System.Data.CommandBehavior)  [500] Could not execute the specified command: The defined query is null. : "UserViews"."variables"==========================================================================================================================We received the following connection string from our IT department--------------------------------------------------------------------------------------------------------------------------curl --location 'https://xxxxxxxxxx.com/um/users/graphql' \--header 'accept: */*' \--header 'Referer: h

61
Thomas Lind
Community Manager
B
Participant
Boglarka BaranyParticipant
asked in REST APIs
API Rest Pagination for Freshdesk

Hi, is there anyone who managed to get the Freshdesk pagination working? I tried different ways but it is not working for me. Let me just describe what I did so far.trying with using Query Parameters and {TX_NextPage}, I tried using that since the freshdesk url is very easy to adjust with the page number, so I added this:My URL is:Pagination should look something like this https://[domain].freshdesk.com/api/v2/tickets?page=[number]So, I added in the connection settings first the pagination rule which looks like this:and I added the endpoint later for tickets.This didn’t work, so I tried the same but adding it in the endpoint with Override pagination rules, unfortunately that didn’t work either. Any other parameters, such as pagesize, or include-stats works, perfectly fine, but the pagination simply doesn’t. So after trying this two, I tried another way. Trying using the header link from response. The query response posts the next page link in the headers, so I tried utilizing that setu

16215
B
Participant
J
Starter
jasperpStarter
asked in REST APIs
Passing a dynamic value as an additional column next to the output of the call it is used in?

I am using a Power BI endpoint (https://learn.microsoft.com/en-us/rest/api/power-bi/datasets/get-refresh-history) where I need datasetIds to get the refreshes of that dataset. I am using the TimeXtender REST data provider, in which I loop over a list of dataset ids using a dynamic value. The problem is that in the output of the Get Refresh History endpoint the dataset Id is not included.Therefore, my question is: Is it possible to pass a dynamic value used in a call as an additional column next to the output of the call? I don't see any option for this in the portal. If I were to extract the data using Power BI, I would do the call for every row in a table containing the required dataset Ids and expand the resulting column. This way, the original table column containing the dataset Ids will always be related to the dataset refreshes. Can I do the same using TimeXtender?

814
M
Contributor
MartinMemelink
Contributor
MartinMemelinkContributor
posted in REST APIs
REST data source multiple XSLT tables performance test

The TimeXtender REST Data Source has the ability to add an API endpoint with table flattening in multiple ways: either adding the endpoint once with multple tables or adding the same endpoint multiple times. I've done some tests to find out which is fastest.The test was done on an API with an unstructured JSON data source, with root nodes on multiple levels where the XSLT Table Builder can iterate over. This means I needed to add 4 flattened tables on the same endpoint, each with different root nodes. Version numbers were REST provider version 9.0, TDI 6935.1, with Ingest running on and Azure VM and storage on ADLS Gen 2.Two ways of setting up the same endpoint with four tablesMy hypothisis was that 1x endpoint with 4x tables would be quicker than 4x endpoints with easch 1x table, because TimeXtender would call the API once and the multiple XSLT tansformations can happen on the same result data, rather than the API being called multiple times which would add unnecessary tansfer of data

291
Thomas Lind
Community Manager
Stijn Verhoeff
Explorer
Stijn VerhoeffExplorer
asked in REST APIs
Error when Importing API Swagger

We are using the new 'Import Swagger/OpenAPI’ feature in the TX REST Data Source (absolutely loving that btw), but are encountering an error.  When importing the URL for a Weather API, we receive the following error message:Error: Exception Type: Microsoft.OpenApi.Readers.Exceptions.OpenApiUnsupportedSpecVersionException Message: OpenAPI specification version '3.1.0' is not supported. So far we've had no trouble importing Open API spec 3.0.0 documentation. Is there a compatibility issue with the latest 3.1.0 spec?

1265
Thomas Lind
Community Manager
anders.e.jonsson
Contributor
anders.e.jonssonContributor
asked in REST APIs
REST Data source - How to set replace value in Table builder?

Hi,I’m trying to use the transformation Set replace value in the Table Builder. Described in tutorial like this: I tried a simple SQL string function (LEFT(NodeName,5). It looks proper in the XSLT Output: The execution worked fine. No errors. But both columns PatientNameHash and PatientName produces the same result in the Ingest table. The full name.Anyone who knows how to format a transformation in Set replace value?Is the content of the template “string-replace-all” available for viewing?BRAnders

6910
anders.e.jonsson
Contributor
J
Contributor
juriaan.hensbroekContributor
posted in REST APIs
REST API with Pagination (MoreApp)

Hi all! This morning, I retrieved data with the REST API of MoreApp.com. The API is quite straightforward. I encountered some challenges that I'd like to share with you. If there’s anything incorrect in this description, please let me know so I can adjust it.PreparationI am using the TX REST connector version 7.1.0.0.You will also need an API key, which must be created by the administrator in the app.The data I need to retrieve is located at the base URL: https://api.moreapp.com/api/v1.0. The specific data I am fetching is "submissions," or filled-out surveys. The POST API used to fetch this data is structured as follows:https://api.moreapp.com/api/v1.0/customers/{customerId}/forms/{formId}/submissions/filter/{page}Customer is fixed. FormId needs to be looked up. Page is required for pagination.Authentication is achieved by including the X-Api-Key in the header.Step 1 – Retrieve the correct FormIdsYou can do this via Postman or TimeXtender. It is a simple GET API:https://api.moreapp.co

2131
J
Contributor
anders.e.jonsson
Contributor
anders.e.jonssonContributor
posted in REST APIs
Hooray for TimeXtender's REST Data source

HI,For the first time in my life, I have enjoyed working with a REST API 😁.It is actually a pleasure to use TimeXtender's new REST data source now.Swagger import, Dynamic values, Table builder etc.There will be more to be desired of course, but hats off to the developers who built it and to Thomas who have made tutorials that are comprehensive and easy to understand.Nice job! 🎉BRAndersP.S. It feels good to be undividedly positive once in a while too 😊

470
anders.e.jonsson
Contributor
E
Starter
EivindJStarter
asked in REST APIs
Rest API with text/plain response

Hello,I'm working with a REST API where the response is a valid JSON but has a Content-Type: text/plain. The response looks like this:[{"OrderId":"46D2A6BD-8B34-4F55-B816-B90017CDBA28","OrderNumber":131,"DeviceId":"POS41232","VendorId":1,"VendorName":"Test Facility","StoreId":114}]However, the log shows the following:2025-01-10T15:33:16.340+01:00    2    [1|Q-Id]    [HTTP|Res: 0] HTTP/1.1 200 OK, 1615 Bytes Transferred2025-01-10T15:33:16.340+01:00    2    [1|Q-Id]    [HTTP|Res: 0] Request completed in 676 ms.2025-01-10T15:33:16.344+01:00    3    [1|Q-Id]    [META|Schema: JSONValidation] https://pos.no/getsales is not a valid JSON resource.2025-01-10T15:33:16.345+01:00    3    [1|Q-Id]    [META|Schema: JSONValidation] Invalid JSON markup. Expected json, but instead found [text/plain; charset=utf-8]. To attempt to fix this, I set Accept: application/json in the request headers, but this results in a response wrapped in a string, like this:"[{\"OrderId\":\"46D2A6BD-8B34-4F55-B816-B90017CD

1354
E
Starter
B
Contributor
BennyContributor
asked in REST APIs
REST connector cashing folder contains a data_.raw and a data_.xml. The result is no data

Hello, I want to get metadate from my Azure datalake using their Blob API. I wasn't seeing any data in the Ingest storage so I turned on cashing to file, to try to see what's happening.  There are three files in my cashing folder: Data_.raw: The return of the call, i.e. my actual data. This look excellent, except that it's a .raw file. Contents: <?xml version="1.0" encoding="utf-8"?><EnumerationResults ServiceEndpoint="https://xxxx.blob.core.windows.net/" ContainerName="datalake"> <Prefix>my_prefix</Prefix> <Blobs> <Blob> .... </Blob> </Blobs> <NextMarker/></EnumerationResults>   Data_.xml: Basically the same as the Data_.raw, but with the content of Data_.raw as the data of a value-element. The data also contains the XML header (so now the document has two headers) and the brackets have been encoded (i.e. all the `<` are now `<`).  <?xml version="1.0" encoding="utf-8"?><Table_flattening_name

775
Thomas Lind
Community Manager
B
Contributor
BennyContributor
asked in REST APIs
REST connector can't handle empty return bodies

I have two particular use cases where I would like the TX REST connector to be able to handle nothing being returned. In one case I've configured the portal to do a PUT request. PUT's generally don't return any body. In a second case, the API is just configured to do this sometimes. We get ID's from another endpoint that we are then supposed to use dynamically like: endpoint/{ID}. The problem is that the source system can have phantom ID's, meaning that ID=13 doesn't really point anywhere. endpoint/13 then returns just a completely empty body. In both cases the problem seems to be that the connector can't handle this. We get back:Failed to execute endpoint 'xxx':Unexpected character encountered while parsing value: }. Path 'TX_Autogenerated_Element', line 1, position 28.Going of the error message, it would seem that the connector is assuming a json was returned and automatically starts trying to convert is somehow.  I need to be able to handle these situations somehow, since I have no

9210
Christian Hauggaard
Community Manager
D
Contributor
DylanW.Contributor
asked in REST APIs
API with redirect cookie

I have an API with the following documentation:• https://baseball.help.trumedianetworks.com/baseball/data-pro-api-docs According to the API documentation, a token must be generated and included as a parameter. This is done using a master token provided by the supplier. When testing in Postman, I receive a response in CSV format; however, the same does not work in TimeXtender. In Postman, the request automatically generates a header "cookie" containing an access token (through redirection). Is it possible to use a cookie container with a redirect option? In cases where a query is redirected to another URL and an authentication cookie obtained from the original URL needs to be set in the redirected request? If so, is this option available in TimeXtender's REST or RSD functionality?

747
D
Contributor
rory.smith
TimeXtender Xpert
rory.smithTimeXtender Xpert
asked in REST APIs
Get value of parent node instead of expanding to children

I am trying to achieve something complex in the TX REST connector using table flattening.I have the following JSON response: [    {        "id": 1,        "submitted": "2024-06-26T12:11:42+02:00",        "answers": [            {                "question": {                    "id": 3,                    "label": "How do you evaluate this?",                    "type": "SINGLE"                },                "answer": 9            },            {                "question": {                    "id": 4,                    "label": "How do you rate the following elements?",                    "type": "MATRIX_SINGLE_CHOICE"                },                "answer": [                    {                        "ids": [                            55                        ],                        "labels": [                            "Drinks"                        ],                        "value": [                            "Good"                        ]                    },     

1102
rory.smith
TimeXtender Xpert
L
Contributor
Leo RogemanContributor
asked in REST APIs
Paging and Dynamic value REST (Rest ODX)

Hello,We have a REST API where we use both Dynamic Value and Pagination (replace URL). The issue is that the paging works fine but only considers the first Dynamic Value and skips the rest. The final result then returns all pages for the first dynamic value and no rows for the rest. Further we also use Table Flattening as well as the Exhaustive Metadata Scan Option.  How can we make it loop through all dynamic values as well as keeping the paging option? API request:https://{base_url}/{company_url} Paging:Replace URL with {nextLink} type XPath Dynamic Value query:SELECT company_url FROM [MDW_Dev].[SysTransform].[Company_information]

39720
Pontus Olausson
Contributor
RobvdBrink
Starter
RobvdBrinkStarter
asked in REST APIs
Query Slicer is not working for more than one location

Hello all,I am currently trying to retrieve all Google Reviews for multiple locations for one of my clients, who operates 35 locations. Some of these locations have over 50 reviews, and since Google Reviews uses pagination through a nextPageToken for more than 50 reviews, I need to handle this pagination effectively.The client is running TimeXtender version 20.10.52.64, and I am using the CData connector version 24.0.8999.0. I have reviewed the documentation on the TimeXtender support pages about nesting an API call and utilizing pagination. I am attempting to set up the Query Slicer to loop through the locations and retrieve all reviews per location, but I am encountering difficulties.Here’s what I have set up so far:I created two .rsd files:locations.rsd: Retrieves a list of all location IDs. This returns 35 locations, as expected. locationsReviews.rsd: Retrieves all reviews for a given location. This works correctly when I test it, returning 397 reviews for one location ID.(I've inc

562
RobvdBrink
Starter
B
Contributor
BennyContributor
asked in REST APIs
How to configure an REST API endpoint with this kind of authorization?

The below image is the documentation for my endpoint. I can't get this to work. When I configure this in the portal I get back a 415 error. Any general guidelines on how to configure this? Update 2024-07-22The regular way:I’ve been doing some additional testing. Here's a more detailed description of my findings/problems. The API wants to receive a JSON body like so:{ "grant_type": "authorization_code", "code": "abc***123"}I tried to add fill out the portal like this:This doesn't work and returns the 415 error.What should I fill out in stead? My cicumvention (doesn't suffice). I configure one endpoint (access_token) to be a POST request (the request that will give back my bearer token). I then configure a second endpoint (Products) and use a dynamic value based on access_token and use it in the header Authorization. See images below.A POST request that will return my bearer token.A GET request that uses the bearer token value returned by the previous endpoint.This method does “wor

24613
B
Contributor
R
Starter
r.brummansStarter
asked in REST APIs
Authorization with bearer token and json body

I am getting a bearer token when i am running the json code below with the specified url, but i don`t know how to implement this json body in TimeXtender, is there any documentation available or a solution for this? {   "id": "",   "language": "en",   "data": {     "resourceType": "AUTH",     "item": {           "loginName": "api@user",            "password": "password",           "module": "API"     }   } }

1664
R
Starter
R
Problem Solver
RLBProblem Solver
asked in REST APIs
Nested API calls maxes out?

Hi,As mentioned here https://support.timextender.com/data-sources-112/advanced-rsd-file-options-884?postid=7688#post7688 I'm having some issues with nested API calls using the CData REST provider. It looks like it maxes out at 1,000 calls per iteration. Is this the expected behaviour or is there a setting I haven't found?Thanks!

849
R
Problem Solver

Badge winners

Show all badges
Terms and ConditionsCookie settings