---
title: "Which one is best client-side or server-side for API access?"  
description: "Which one is best client-side or server-side for API access?"  
author: "Rocky Dada"  
published: 2023-08-30  
updated: 2023-08-31  
canonical: https://www.mindstick.com/forum/159764/which-one-is-best-client-side-or-server-side-for-api-access  
category: "web api"  
tags: [".net", ".net core api"]  
reading_time: 2 minutes  

---

# Which one is best client-side or server-side for API access?

[Explain the concept](https://www.mindstick.com/forum/159605/explain-the-concept-of-unique-key-violation-error) of [API access](https://answers.mindstick.com/qa/33331/how-do-i-enable-api-access-in-salesforce) in the [context](https://www.mindstick.com/forum/23245/what-is-context-in-android) of .NET Core Which one is best [client](https://www.mindstick.com/articles/23198/3-steps-to-ensure-that-your-client-portal-is-impeccable)-side or [server](https://www.mindstick.com/articles/43769/what-is-serverless-architecture-is-it-worth-switching-over)-side for API access?

## Replies

### Reply by Aryan Kumar

The best approach for [API](https://www.mindstick.com/articles/12641/instagram-api-upgraded-to-facebook-graph) [access](https://www.mindstick.com/articles/12994/how-foreigners-can-access-blocked-websites-in-china) depends on a number of factors, including the security requirements of the application, the performance requirements, and the development team's expertise.

**Client-side API access** involves making requests to an API from the client's browser. This approach is often used for simple applications that do not require a high level of security. It is also a good choice for applications that need to be responsive, as the requests can be made directly from the browser. However, client-side API access can be less secure than server-side access, as the requests are made over the public internet.

**Server-side API access** involves making requests to an API from the server. This approach is often used for applications that require a high level of security, such as banking applications. It is also a good choice for applications that need to handle a lot of traffic, as the requests can be made from the server, which is typically located behind a firewall. However, server-side API access can be less responsive than client-side access, as the requests need to be routed through the server.

Here is a table summarizing the pros and cons of client-side and server-side API access:

| Feature | Client-side | Server-side |
| --- | --- | --- |
| Security | Less secure | More secure |
| Performance | More responsive | Less responsive |
| Development complexity | Less complex | More complex |

Ultimately, the best approach for API access depends on the specific needs of the application.

Here are some additional things to consider when choosing between client-side and server-side API access:

- The security requirements of the application. If the application requires a high level of security, then server-side API access is the better option.
- The performance requirements of the application. If the application needs to be responsive, then client-side API access is the better option.
- The development team's expertise. If the development team is more familiar with client-side development, then client-side API access is the better option.


---

Original Source: https://www.mindstick.com/forum/159764/which-one-is-best-client-side-or-server-side-for-api-access

Copyright © MindStick Software Pvt. Ltd. This Markdown version is provided for developers, AI systems, and offline reading.