POST http save Screen with special characters

I try to call the endpoint https://api-worldcheck.refinitiv.com/v2/cases/saveAndScreen in C# with a name which is "RATP Réseaux" but I am returned a 401 but when I change the name to " RATP Reseaux" I have a 200. I think it's because of the "é" character but he encodes it in UTF8.
here is my function which allows you to call api
public async Task<T?> PostRequest<T>(Uri uri, string data)
{
using (HttpClient client = _clientFactory.CreateClient())
{
HttpMethod httpMethod = HttpMethod.Post;
Encoding encoding = Encoding.UTF8;
string contentType = "application/json";
HttpRequestMessage httpRequest = new HttpRequestMessage(httpMethod, uri);
Dictionary<string, string> headers = AuthHeadersBuilder.GenerateAuthHeaders(
apiKey,
apiSecret,
httpMethod.Method.ToLower(),
uri,
contentType,
data);
foreach (KeyValuePair<string, string> header in headers)
{
httpRequest.Headers.Add(header.Key, header.Value);
}
httpRequest.Content = new StringContent(data, encoding, contentType);
httpRequest.Content.Headers.ContentType = MediaTypeHeaderValue.Parse(contentType);
var response = client.SendAsync(httpRequest).Result;
response.EnsureSuccessStatusCode();
var jsonContent = await response.Content.ReadAsStringAsync();
return JsonConvert.DeserializeObject<T?>(jsonContent);
}
}
and my body is :
{
"groupId": "5jb6eq4nmdc41ihi4jaus2r156",
"providerTypes": [
"WATCHLIST"
],
"nameTransposition": true,
"caseScreeningState": {
"WATCHLIST": "INITIAL"
},
"cases": [
{
"entityType": "ORGANISATION",
"name": "SNCF Réseau",
"secondaryFields": [
{
"typeId": "SFCT_192",
"value": "FRA"
},
{
"typeId": "SFCT_6",
"value": "FRA"
},
{
"typeId": "SFCT_193",
"value": "FR-RCS"
},
{
"typeId": "SFCT_191",
"value": "412280737"
}
]
}
]
}
Do you have a solution ?
THANKS,
PRAK Billy
Best Answer
-
Hello,
Letters with diacritical marks encoded in utf-8 can have a length of 2.
"é".length => 2
This is likely causing your 401 error, depending on how your length calculation is made.Try removing diacritics before any processing is done or try adjusting your length calculations to account for the diacritics.
See:
Issue with special characters in World Check One Screening - Forum | Refinitiv Developer Community
Try using our Postman collection to quickly test out requests and verify responses:
LSEG World-Check One API Guide
Included in this link is our sample code which should help you account for diacritics.
Let us know if you require any assistance with your authorization header code.
Thanks,
WC1 API Team
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 684 Datastream
- 1.4K DSS
- 615 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 249 ETA
- 554 WebSocket API
- 37 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 643 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 26 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 192 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛